-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
example/intro scripts confusing #22
Comments
The naming convention lies in the history/ organic growth of pyplis. The example scripts ( |
maybe example_%i_ and intro_%i_ would be somewhat more intuitive? |
Thanks for your thoughts on this! I agree that the names could be clearer (as in other parts of the pyplis API, cf. #20), but I would like to keep the names of the scripts as they are, since they are referred to in the paper (see Table A2. therein). On the longer term, I would like to move away from this set of example scripts and have new and better examples / tutorials in the form of jupyter notebooks (potentially online in combination with a JupyterHub server to run them in a virtual env from anywhere). I close this issue now and will open a new one that will pick up the tutorial notebook idea. |
I dont understand the difference between an example and an intro script, neighter in content nor in file name.
I can guess from the runner scripts that
ex0_
are intro scripts andex[<0]_
are example scripts, but maybe this distinction could me made clearer.RUN_EXAMPLE_SCRIPTS.py
RUN_INTRO_SCRIPTS.py
In any case, what is the exact distinction between an example scripts and an intro script?
The text was updated successfully, but these errors were encountered: