Conversation
|
Warning! No news item is found for this PR. If this is a user-facing change/feature/fix, |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #6 +/- ##
=======================================
Coverage 50.00% 50.00%
=======================================
Files 2 2
Lines 18 18
=======================================
Hits 9 9
Misses 9 9 🚀 New features to boost your workflow:
|
sbillinge
left a comment
There was a problem hiding this comment.
this code looks pretty ugly. Can we work from the UCs and figure out what functionality we need and separate the functionality. These look like scripts not well architected code. They seem to mix up I/O and functionality and the functions are not well separated and doing only one thing. It is not even evident to me what is the purpose of this? WHich UC is being implementd?
|
Thanks for pushing the PR early. Let's close this and revisit it in a more structured way. |
|
This was the code we used for the poster, which you mentioned I should make a draft PR for. I have a lot of cleaning to do. |
|
I see, gotcha. It's ok to leave it here for safe-keeping but make multiple new clean PRs for the different functionality and don't edit on this one. We want general functions that handle different aspects ofthe UC that we will reuse across all the UCs, for example loading a single CIF to the ASE structure object (there should be an ASE function to do that that we can wrap), then doing the same thing for a set of CIFs, then different functions for building sets of CIFs (use glob with filters? Allow the user to specify a list? that but the list is in an input file on disc?) and so on. then our code can just operate on sets of structure objects etc. Clearly that functionality will be reused across all the different metrics. And so on. |
Convert CIFs to PDFs and compare.