ai4er-cdt / ai4er-cookiecutter Goto Github PK

Hey, the magic lines currently given at

notebooks/README.md are:

%load_ext autoreload             # loads the autoreload package into ipython kernel
%autoreload 2                    # sets autoreload mode to automatically reload modules when they change
%config IPCompleter.greedy=True  # enables tab completion

But they break because python seems to not allow any characters after a magic command.

https://stackoverflow.com/questions/47577596/modulenotfounderror-no-module-named-autoreload

We could move the comments to separate lines or put them above the code in the notebooks/README.md file

We could add

    // Include [extendedSummary] tag in automatic docstring generation
    "autoDocstring.includeExtendedSummary": true,
    // Start each docstring on a new line
    "autoDocstring.startOnNewLine": true,
    // format docstrings using sphinx

to .setup_scripts)/vscode_settings.jsonc

Hey, I was setting up a public repository on jasmin-sci3 today, but it wouldn't push to remote. It would just hang until it timed out.

The remote settings were initially:

(base) [[email protected] MLBayesInfer]$ git remote -v
origin  [email protected]:sdat2/MLBayesInfer.git (fetch)
origin  [email protected]:sdat2/MLBayesInfer.git (push)

Using:

remote set-url origin https://github.com/sdat2/MLBayesInfer.git

I changed this to:

(base) [[email protected] MLBayesInfer]$ git remote -v
origin  https://github.com/sdat2/MLBayesInfer.git (fetch)
origin  https://github.com/sdat2/MLBayesInfer.git (push)

It then it worked perfectly. Is there a reason to prefer the [email protected]: syntax? If not, it might be worth changing to https:.

It seems that the file: prefix needs to be removed from the pip install within the environment.yml file due to a change in pip syntax:

https://stackoverflow.com/questions/68571543/using-a-pip-requirements-file-in-a-conda-yml-file-throws-attributeerror-fileno/68586065#68586065

See here for inspiraiton: https://drivendata.github.io/cookiecutter-data-science/

• flake8 linting

• black formatting

• jupyter black

• potentially github CI

The cookiecutter asks the user whether to link to a data directory. The JASMIN documentation asks users to not create inter-volume symlinks, e.g. between the home directory and the GWS. This is perhaps something the user should be warned about.

They suggest using environment variables instead. It would be handy to do this automatically; I think conda can handle environment variables.

See https://help.jasmin.ac.uk/article/176-storage#intervolsymlinks

Hi all,

I have an embarrassingly basic question about how to use this cookiecutter repository. Let's say that one has coded up various functions in separate files and directories under src. How does one then import all the code under src as a module? I haven't tried to write my own module before, so I think I'm missing some basic ideas here. Most of the tutorials I've found online assume that one's "module" is contained in a single .py file, which obviously isn't the case here. Thanks in advance for any help/clarification that you all can provide!

Hydra seemed so cool. Maybe add it as default. I realise this is a bit opinionated.

• How to use

• What is cookie cutter in general (https://www.youtube.com/watch?v=96fpONwXjGA)

• When to use

Again a really nice discussion & inspiration here: https://drivendata.github.io/cookiecutter-data-science/

Hello,

I am trying to use the ai4er-cookiecutter to make a new repository following the command-line approach. I followed the instructions to create a conda environment:

conda env create --prefix=./env -f requirements/environment.yml

which seemed to work okay. The setup script then suggested this command:

>>> New conda env created. Activate from project directory with:
conda activate ./env

However, this command returns an error:

conda activate ./env
-bash: syntax error near unexpected token `('
-bash: syntax error near unexpected token `('

I did some quick Googling, but I didn't find a solution. FYI: I'm using bash on a MacBook, via the terminal.