Conversation
|
@ladinesa This is meant to be a quick solution for some users who belong to a large collaborative project. I set this up so that they can meet some deadline for a report/publication, but will then set them up on a route to creating a proper plugin with the new schema. I am sure that my approach here is hacky, but also I do not want to spend too much more time on it, so if you can identify the essentials to make it acceptable in your opinion, that would be great. I am waiting for some feedback from my data steward contact, but I think we can mostly still finalize in the mean time. |
|
Maybe add a test data, just maybe parse it in test no need to assert any quantity. |
Pull Request Test Coverage Report for Build 15704995843Details
💛 - Coveralls |
Question about the logger for tests: If I leave my logger statements as they are, i.e., using the input logger from the parse() function, then the logger output shows up in the GUI when I launch locally, but when I run pytest the logger is None. On the other hand, if I instead set Do you understand this? What is the correct approach? |
|
in |
This is basically a shell parser so that some users can upload DFT and DMFT data from the RSPt software and have minimal search capabilities, etc. They will then work on developing a "real" parser for their code which can later be used for reprocessing