-
Notifications
You must be signed in to change notification settings - Fork 0
adjusted xyz_to_mol to take in different forms of xyz data #5
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
Conversation
jwaldrop107
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 think the changes here are mechanically fine, but I would actually advise introducing a new module entirely. Basically, split what you have here into one module whose singular focus is to parse XYZ data from a string, and another one whose purpose is to read in XYZ data from a file. The file reader module can then use the data parser as a submodule. This scheme allows for clarity of purpose in the modules and distinct names to describe what they do ("XYZ To Molecule" and "XYZ File To Molecule" for instance).
Regarding the completeness of the test cases, they seem sufficient to me.
|
Agree with @jwaldrop107. |
|
I separated out the modules, the only thing I'm not super confident about is the "try, catch" code. |
jwaldrop107
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.
Right track, but there are some further changes I'd recommend.
jwaldrop107
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.
LGTM
|
🚀 [bumpr] Bumped! |
Is this pull request associated with an issue(s)?
No
Description
I wanted to adjust the xyz_to_mol module to be able to take in data from the input as a string instead of just as a file.
TODOs