-
Notifications
You must be signed in to change notification settings - Fork 0
Update Documentation #87
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
base: main
Are you sure you want to change the base?
Conversation
hannahlanzrath
left a comment
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.
I have left some comments, thanks for the nice overhaul so far!
.vscode/launch.json
Outdated
| @@ -0,0 +1,15 @@ | |||
| { | |||
| // Use IntelliSense to learn about possible attributes. | |||
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.
I think we can ditch the IntelliSense entry?
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.
Yes, I actually didn't mean to include this .vscode directory in the CADET-RDM push at all. It was automatically generated while I changed my configurations. I will remove the whole directory with my next push.
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.
Ah I see, you can just add .vscode to .gitignore in the RDM folder, that will solve it!
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.
That's right, I didn't even think of that! Thanks
AUTHORS.md
Outdated
| @@ -0,0 +1,14 @@ | |||
| # Contributors | |||
|
|
|||
| The following individuals have made significant contributions to the CADET-RDM software and are listed in *chronological order*. Together they form the "CADET-RDM authors" as mentioned in the copyright statements. | |||
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.
I would leave the Introduction Sentences out here, so we just have "Contributors", then the Names.
Order: Ron, Hannah, Jo, Katha, Daniel, Eric
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.
Okay, no problem. I will also change this in the cookiecutter template. This could also be changed in the CADET-Core AUTHORS.md if necessary.
| To share your project code and results with others, you need to create remote repositories on e.g. | ||
| [GitHub](https://github.com/) or GitLab. You need to create a remote for both the _project_ repo and the | ||
| _results_ repo. | ||
| To share your project code and results (`output`) with others, you need to create remote repositories on e.g. |
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.
Passive speech would be better here, so e.g.
"To share a project code and results (output) with others, a remote repository has to be created..."
Just to avoid "You"
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.
Got it, the direct "You" is currently used very often in the documentation and the descriptions and comments in the source code. I can try to at least change the wording in the documentation.
|
|
||
| Once remotes are configured, you can push all changes to the project repo and the results repos with the | ||
| command | ||
| Once remotes are configured, you can push all changes to the project repository and the output repository with the following command from within the project repository: |
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.
Same here, so something like
"Once remotes are configured, all changes can be pushed to the project repository and the output repository with the following command from within the project repository..."
Co-authored-by: Hannah Lanzrath <h.lanzrath@fz-juelich.de>
Co-authored-by: Hannah Lanzrath <h.lanzrath@fz-juelich.de>
Co-authored-by: Hannah Lanzrath <h.lanzrath@fz-juelich.de>
Co-authored-by: Hannah Lanzrath <h.lanzrath@fz-juelich.de>
Co-authored-by: Hannah Lanzrath <h.lanzrath@fz-juelich.de>
extend documentation to explain creation of new directories with path_to_repo, change parameter name from output_folder_name to output_directory_name, modify descriptions to use path and directory instead of folder Fix Unicode Error by escaping path name in function description by using "\\U..." instead of "\U..." rename output_folder to output_directory Change remote path in test_git_adapter.py function try_initialize_from_remote from git@github.com:ronald-jaepel/rdm_testing_template.git to git@github.com:cadet/RDM-Testing-Template.git to account for renaming changes Update location for remote repository rdm-testing template Explain optional cookiecutter support in more detail Modify documentation: expand upon introduction, add description of file structure, rename CLI documentation Fix typos Change output_repo_name to output_directory_name Update branch name documentation, change folder to directory in documentation and descriptions Add AUTHORS, CITATION, CODE_OF_CONDUCT, SECURITY.md Remove unimplemented cli function to load results from another repository via cadet-rdm-cache.json from documentation Expand rdm clone documentation Change AUTHORS.md order, use indirect speech in documentation, fix function parameters in documentation Modify getting started, add .vscode to gitignore Add Introduction in docs Add Git-LFS installation guide, modify documentation structure Add myst_parser, modify bibliography.md to cite all references Add image directory, modify image creation with sphinx syntax Co-authored-by: Hannah Lanzrath <h.lanzrath@fz-juelich.de>
Co-authored-by: Hannah Lanzrath <h.lanzrath@fz-juelich.de>
Co-authored-by: Hannah Lanzrath <h.lanzrath@fz-juelich.de>
Co-authored-by: Hannah Lanzrath <h.lanzrath@fz-juelich.de>
Co-authored-by: Hannah Lanzrath <h.lanzrath@fz-juelich.de>
Co-authored-by: Hannah Lanzrath <h.lanzrath@fz-juelich.de>
Applies naming conventions to comments, docs and variables. Co-authored-by: Hannah Lanzrath <h.lanzrath@fz-juelich.de>
Co-authored-by: Hannah Lanzrath <h.lanzrath@fz-juelich.de>
Co-authored-by: Hannah Lanzrath <h.lanzrath@fz-juelich.de>
109c0e3 to
37fd84f
Compare
This PR makes changes to CADET-RDM to address part of the To-Dos from Issue #80 and #76, improve readability and inconsistent nomenclature.
General changes
path_to_repoChanges needed to address failing tests
try_initialize_from_remote()(Line 157)"output_folder_name". This line in the .json file would have to be renamed to"output_directory_name"to fix the failing testDocumentation checked and modified
Documentation changes
getting-started.md
rdm checkandrdm pushCommand Line Interface
Inside the output directory, new empty directories with the names of the imported project and output repositories are created. This takes place in a new branch. No other files are modified, including cadet-rdm-cache.json.
Currently only useful to copy specific files, e.g. .py-files within a new branch to the output repository (by specifying url=source_project/output/specific_file.py) while also creating empty directories with the names of project and output repository from the source repository.