auto-dl / auto-dl

Auto-DL helps you make Deep Learning models without writing a single line of code and giving as little input as possible.

Introducing the "Futuristic" way of building Deep Learning Models

---

Auto-DL is just DL but without code. 🤩

Building deep learning models may take a lot of time. But not with AutoDL.
Automate your meta-work so that you can focus on building your models without the hassle of writing code.

• ✨ Use our interactive model builder and AI powered suggestion system to quickly whip out a working DL model. ✨

• ✨ Trained your model for multiple hours and found out that it's bugged? Not anymore. With AutoDL's AI ecosystem validate your model before you train it. ✨

• ✨ Host your model just as easily as you created it. ✨

Hacktoberfest Guidelines 📝

• If an issue is not "assigned," you can assume that no one is working on it (may NOT be true). So to be sure, you can ask the following:

  • Can I take this up?
  • Also, mention a rough deadline until which you plan to fix the issue
  • (Optionally) Potential fixes DO NOT CREATE a pull request FIRST if someone else is working on it then your efforts might be wasted. Claiming doable and unclaimed issues should be the priority

• Conventional commits in the PR title are a must

• For frontend, while creating a pull request attach a screenshot of the change

• Last but not least, one pull request to fix a typo is fine, but 5 pull requests to remove a stray whitespace is not (reference).

User Guidelines 📋

The docs are the perfect place for you to start getting used to Auto-DL.

Want to setup locally? 🏠

• Start with our getting started docs.

• The doc didn't help? Join our slack and ask your questions!

Just want to get a gist of "How to use the application"?

• You can directly jump to the user guide :)

Developer Guidelines 👩‍💻

The contributing guidelines hosts all the information about building Auto-DL from source, how to contribute code and documentation, who to contact about what, etc.

Get started with Auto-DL (For Developers) 🌐

Setup Auto-DL:

• Bare-metal way
• Using Docker

---

Features/Enhancements planned 💡

• Improve the UI and UX.

• Show model training related stats on the frontend.

• Visualization and data preprocessing steps.

• Model Explainability.

Contact 📧

You can find us on or on or join our community on Slack.

Have doubts? 💬

Read the FAQ or send us a mail at [email protected]

For more details, visit our website

---

Contributors 💯

Copyright and Licensing ©

GNU General Public License v3.0

auto-dl's Issues

Basic framework for the docs

Feature Request

Is your feature request related to an existing Issue or a new implementation?

Feature Description

Basic framework for the docs

Error while executing " git submodule update " command.

Add forgot password backend route

A requirements.txt needed

A requirements file to install all dependencies is needed

Remove "chat on gitter" badge from Readme

Generate routes fails

Bug Report

Need to update generate route. It fails as its as per v0

Current Behavior

Empty code file generated

Expected behavior/code

Code generated as per the created model

⚙️ Environment

• Python version(s):
  • good: 3.8
• OS: Windows 10

Add issue and PR tempaltes

2 issue templates

1. Bugs
2. Feature Requests

And a template with a basic checklist for PRs is needed

Make endpoint for generating code from f2b json

Correction in readme

Found an inaccuracy in the How To Run section.

- pip install requirements.txt 

+ pip install -r requirements.txt

It could also be that just my version needs the -r option? Will need info from others.

Make a route to check if model compiles correctly (keras)

Add new app for authentication

Add training endpoint

Requested-by : Sameer Ansari [email protected]

Make a django project

Make structure for backend app

Update requirements.txt

Add the following to requirements.txt

1. python-dotenv
2. pymongo
3. bcrypt
4. dnspython

Add route to create new project

Don't forget to save metadata

React app needed

Add route to get fetch projects

Start new front end application

Just output of create-react-app or something similar would be enough

The name of the app can be "FrontEndApp" to keep consistency with the back end

Update DLMML Submodule

Update the submodule head to point to modular API code for python/keras/

Incorrect path in README

Bug Report

Step 3 of README.md

When I try to install the Project and run the FrontEndApp, the path mentioned in the README file is:

cd FrontEndApp
npm install

However, it must be noted that the folder in which package.json file exists is actually at the path FrontEndApp/v1-react. I understand this is only going to be the case while the project is under development, however for someone not used to npm this might be a time-consuming error.

Current Behavior

The cmd (rightfully) points out that package.json file was not found, and hence the node_modules are not installed.

Expected behavior/code

To make it easier for all contributors, the README should direct the user to the correct path and prevent any confusions for a beginner.

⚙️ Environment

• OS: Windows 10

Possible Solution

Replace the above section with

cd FrontEndApp/v1-react
npm install

Linting Errors

Bug Report

When I tried to set up eslint on save, for the repository, these are the issues that were encountered. A lot of those can be, and will be, converted to warnings. However, I felt it was important to list all the linting errors so that the contributors can take care of it and thus the linter can be merged in the project.

Current Behavior

After running npm start, a stream of linting errors is generated that should be taken care of. I am attaching the pdf file here.
AUTO DL SCREENCAPTURE.pdf

Expected behavior/code

Those practices as listed should be taken care of, and the respective errors be cleared at the earliest.

Possible Solution

Additional context/Screenshots

Here's the list of all possible rules for eslint

Add package-lock.json to gitignore

Bug Report

Current Behavior

Gives some dependency error

Expected behavior/code

front end server should start

⚙️ Environment

• OS: Windows 10

Add backend logout route

Add backend login route

Add "Join our Slack Community" badge to readme

Please find how it is done ideally in popular open source orgs, "badge" is not a compulsion, just somehow (correct way) link to the slack channel should be there.

Step 1 in react app needed

Routes to save and get layers needed

Feature Request

Is your feature request related to an existing Issue or a new implementation?
Nope

Feature Description

2 routes one to save layers and other to get the layers in step 2

Add route to delete project

Appbar needed for home and all pages with given routes

Integrate react app with backend

Integrate react app with backend for FOSSUnited demo

send path for generated file by dlmml

Create a decorator to verify if the user is authenticated, to protect certain routes

Add backend register route

For registration refer to our meeting minutes:

Add a linter

Feature Request

Is your feature request related to an existing Issue or a new implementation? NO

Feature Description

A linter will ensure that the quality of code is homogeneous throughout all contributions. Later on, we can also add a GitHub Action to verify whether the code has been linted appropriately or not.

Possible Solution

I will try to work with setting up 'ESlint' for the project. And thus the command npm lint or npm run lint can be used for the project.

Appbar needed with logo in login/register

Add verify email backend route

Update slack invite link on readme badge

Add folder creation and caching

Add route to update project metadata

meta.json with

• project name
• lib
• lang
• data dir
• output file name

Add support for training in windows

Feature Request

Feature Description

Currently the train.sh bash file runs when we want to train the generated model. Add such a script for windows as well.

Possible Solution

Make a bash file

Update Readme

Compiler Warnings

Bug Report

Current Behavior

There are a lot of unused imports lying around in the React code (almost 20). The compiler lists all those every time the code is compiled.

Expected behavior/code

All warnings should be properly dealt with such that none appear.

⚙️ Environment

• OS: Windows 10

Possible Solution

Remove all unused imports from the .js files.

Redirect to Home if credentials already exist in local host

Update tensorflow >= 2.3.1

Some serious vulnerability reported by dependabot in 2.3.0

Please update it, test the whole pipeline and make a
"Update requirements.txt" pull request.

Thanks,
Adi

Add route to get details of a project

Details as in layer details

Step3.js pushed with no tags

Bug Report

ESLint failed to compile the file Step3.js

Current Behavior

The file only displays text. But it should be properly enclosed in p tags.

Expected behavior/code

Better formatting. Enclose all text in an HTML tag.

Contributing.md Empty file

Wanted to start contributing to the repository. The README file says read the contributing guidelines before actually contributing, but guess what.

Consider adding contents to the file.

Change request status appropriately

We're sending status in JSON body, but request status is till 200.
Change that to request.status or something like that

Error while registering

Bug Report

can not decode str error

Current Behavior

To replicate:

• Start frontend and try to register

It will throw error

Expected behavior/code

Should register and redirect to home page

⚙️ Environment

• Python version(s):
  • 3.8
• OS: Windows 10

Rearrange README

Feature Request

Is your feature request related to an existing Issue or a new implementation?
NO

Feature Description

The Demo tab in the README should be placed above the How To Run section.

Possible Solution

Create an up-to-date DEMO gif file, and place it above the How To Run section.

Additional context

This enables the user to see the product in working and motivates them to use the deployed version themselves. If they wish to run the project locally, they can always search. But that might not be everybody's objective.