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
Update examples in C and Fortran #242
Conversation
Codecov ReportPatch and project coverage have no change.
📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more Additional details and impacted files@@ Coverage Diff @@
## develop #242 +/- ##
========================================
Coverage 85.69% 85.69%
========================================
Files 23 23
Lines 6069 6069
========================================
Hits 5201 5201
Misses 868 868
Flags with carried forward coverage won't be shown. Click here to find out more. Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
Since users in C and Fortran may be exclusive, I attempted to change directory structure and the names.
Dependency of |
It is done except for |
I agree with that, but can it be structured like:
I'll look into that. Just re-request a review to ping me when you want me to look into it. |
Almost done. One final thing though, why not the following folder structure:
(/example/c_api, etc.) Top example readme tells about what common minimal example is implemented in all 3 and that a complete one is also provided. |
Ok, my final note, fortran files should be |
CI fails because |
Please rebase onto develop. We cannot merge because of merge conflict. $ git rebase origin/develop
$ git status
Check which files are conflicting and how to resolve it
$ emacs example/c_api/README.md
Command may be different because file was moved
Resolve conflicts by editting the blocks:
<<<<< HEAD
Content from origin/develop
=====
Content from branch examples
>>>>>
$ git rebase --continue I can also recommend gitkraken if you don't feel comfortable with the git cli for this. I will add commit fixes on top of this PR before merging when you feel it is ready. |
Co-authored-by: Cristian Le <github@lecris.me>
Co-authored-by: Cristian Le <github@lecris.me>
Co-authored-by: Cristian Le <github@lecris.me>
Thanks for your detailed instruction. No conflict was found in rebase. |
Great. Pre-commit seems to fail Oh, the merge is reporting changes from develop. A rebase would have made it cleaner to review. |
How can I do? |
At this point will have to interactively rebase to drop the merge commit. But basically running I'll handle that later |
I made |
Edit the file extension in the cmake files also.
Yes, you can freely force-push in these situations. Just never force-push the |
Yes, I made it. e2a01d5. |
Is there anything left to do? |
Just to fix git history and cmake. I'll do that tomorrow |
It is clearly difficult for me to do. Thanks @LecrisUT. |
Signed-off-by: Cristian Le <cristian.le@mpsd.mpg.de>
Signed-off-by: Cristian Le <cristian.le@mpsd.mpg.de>
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.
@atztogo I have refactored your branch and fixed the examples. I have noticed that the python example is not equivalent to the others. Could you make some changes there, and if possible add some words to example/README.md
?
You can work on the same branch again by:
$ git fetch
$ git reset --hard origin/examples
Otherwise we can open a new PR for that.
And of course, thanks for all the work on this 😄
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.
Thank you fully 👍 from me. Do you want to wait for @lan496 to review as well?
I have no objection. Please merge if you are ready. |
PR for #236.
example_c
andexample_f
The examples in C seem not so bad. So I just changed the function names of
test_*
toexample_*
.The Fortran code of examples in Fortran was very dirty. I made it a little bit cleaner.
Conceptual examples for
spg_get_dataset
should be written inREADME.md
.Closes: #236