-
Notifications
You must be signed in to change notification settings - Fork 24
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
Draft: BandFragmentJob #130
base: trunk
Are you sure you want to change the base?
Conversation
The documentation used Sphinx Also: There are many relative links in the documentation to other parts of AMS, therefore it cannot be built independently... |
I'm not quite sure how the ADFFragment recipe was ever supposed to work... I think I'm fixing it in with b99ff4a. |
Good idea on the switch to I have also fixed a fair few of the links, although there are still some remaining. I aim to get this as self-contained as possible! |
I have been looking at the example |
Interesting. For me it did not create a valid input file... |
Working on debugging the issue with relative restart paths with Pier at the moment. Perhaps I can make the code much easier when we figure out when relative paths make the calculations crash... |
Found it - for reference, the original fragment job works because when getting the input for the full job (https://github.com/SCM-NV/PLAMS/blob/trunk/interfaces/adfsuite/ams.py#L2244), the So this in a roundabout way is how the dependency is enforced between the full and fragment jobs. I have attached the input file that should be generated by |
This reverts commit b99ff4a.
Ahh, now I understand. Thanks. Just reverted the changes there... |
Writing a BandFragmentJob for pEDA calculations based on the available ADFFragmentJob.
Based on initial work by @hweiske.
Feedback welcome!