-
Notifications
You must be signed in to change notification settings - Fork 0
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
183 add job inheriting #186
Conversation
…ictionary to a Result object
…ild settings for a new job
Looks good. I am wondering does it copy the whole class? So not only the functional, basis set etc. but also dependancies or post/preamples? This could increase the risk of human errors for larger workflows (forgetting to get rid of certain dependancies) |
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.
See comment in the main comment review
Indeed, this will copy the whole object, but I think that should be desired behaviour in this case. If you do not want to have dependencies then the user should make sure that there is no dependency set in the reference Job object. Preambles and postambles should also be copied over in my opinion. |
Nice addition! |
This now works, but we should add some test-cases