-
Notifications
You must be signed in to change notification settings - Fork 202
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
T000 - Talktorial template #85
Conversation
Hi @AndreaVolkamer , This PR is ready for your review. I did not add an general comment on
since I think that Jaime or Jeff wanted to set up a document on best practices anyways, which we will be able to link here in the future. I did referring though to (a) specific PEP8 guidelines e.g. for imports and (b) our template issue. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dominiquesydow awesome, I really like the added information and the highlighted boxes!
I added only very few minor suggestions, feel free to include them. The notebook can afterwards be merged without further approval from my side.
"cell_type": "markdown", | ||
"metadata": {}, | ||
"source": [ | ||
"_The examples used in this talktorial template are taken from __Talktorial T001__._" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe include an actual link to T001?
"source": [ | ||
"<div class=\"alert alert-block alert-info\">\n", | ||
" \n", | ||
"<b>Figures</b>: Place images in the <code>images/</code> folder and include them using Markdown <code>![Figure title](images/some_figure.jpg)</code>. Add a figure caption in the format provided below.\n", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
.. in the format provided above (not below)?
"<b>Relative paths</b>: Please do not use relative paths to example input/output data or images.\n", | ||
"Instead add this talktorial's path to the global <code>HERE</code>. Define all paths relative to this path.\n", | ||
"\n", | ||
"<br/>\n", | ||
" \n", | ||
"If your talktorial has input/output data, please define the global <code>DATA</code>, which points to this talktorial's data folder (check out the default folder structure of each talktorial).\n", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"<b>Relative paths</b>: Please do not use relative paths to example input/output data or images.\n", | |
"Instead add this talktorial's path to the global <code>HERE</code>. Define all paths relative to this path.\n", | |
"\n", | |
"<br/>\n", | |
" \n", | |
"If your talktorial has input/output data, please define the global <code>DATA</code>, which points to this talktorial's data folder (check out the default folder structure of each talktorial).\n", | |
"<b>Relative paths</b>: Please define all paths relative to this talktorial's path by using the global variable <code>HERE</code> and define all paths relative to this path.\n", | |
"\n", | |
"<br/>\n", | |
" \n", | |
"E.g. if your talktorial has input/output data, please define the global <code>DATA</code>, which points to this talktorial's data folder (check out the default folder structure of each talktorial).\n", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a suggestion, I felt the before sentences were somehow duplicated.
" [molecular_weight, n_hba, n_hbd, logp, ro5_fulfilled],\n", | ||
" index=[\"molecular_weight\", \"n_hba\", \"n_hbd\", \"logp\", \"ro5_fulfilled\"],\n", | ||
" )" | ||
] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we add before/after the example function, to use meaningful function and parameter names?
"<b>Useful checks at the end</b>: \n", | ||
" \n", | ||
"<ul>\n", | ||
"<li>Clear output and rerun your runtime. Does it finish without errors?</li>\n", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"<li>Clear output and rerun your runtime. Does it finish without errors?</li>\n", | |
"<li>Clear output and rerun your complete notebook. Does it finish without errors?</li>\n", |
Great, thanks, @AndreaVolkamer - all your suggestions are integrated. Will merge now. |
Details
TODO
Update template w.r.t. @AndreaVolkamer's suggestions (that she send via PM - copied here):