[mic step1] Overview

[mosoriob]

Pipeline

1. The user must go to the directory where the code is. The directory must contain the data. We don't support data outside this directory

2. The user must type

   mic encapsulate step1 <path_to_user_execution_directory>

3. MIC detect the framework/language (we support python and conda) MIC prints

   Success/Failed

4. MIC renders the docker file and dependencies in the MIC component directory.

5. MIC build the docker image

6. MIC run the image:

7. The user sees the message:

   
   You are in a Linux environment Debian distribution
   We detect the following dependencies.

• If you install new dependencies using apt or apt-get, remember to add them in Dockerfile
• If you install new dependencies using conda, MIC is going to detect them
• If you install new dependencies using python, MIC is going to detect them

Please run your model.

3. _MIC create a new directory in the MIC component directory with the data, src, mic.yaml_

Issues:

- [ ] ~~MIC creates a directory to store the components: `$HOME/mic`~~ 
- [x] MIC step 1 must expect argument: `path_to_user_execution_directory`~~  and two prompts question: name and description~~ 
- [ ] ~~MIC creates a new directory in the MIC component directory using the name~~ 
- [x] MIC detect python dependencies
- [ ] MIC detect conda dependencies
- [x] MIC build the image
- [x] MIC run the image: 
  1. Interactive mode, tty mode
  2. Mount -v <MICcomponentdirectory>:/tmp and <mic_component_directory>:$HOME
- [x] Add welcome message using click

[issue-label-bot[bot]]

Issue-Label Bot is automatically applying the label feature_request to this issue, with a confidence of 0.82. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

[dgarijo]

I like the direction where this is going, but I have some questions:

• Where is the mic component created? I think we should point to the path of where the code/data is, but the user should know that they are creating a mic component in a different path. It's like selecting the project (mic component) path/name.
• What happens if users have data in different path than code?
• This workflow does not capture the selection of inputs and parameters. Is this a later step?