Closed yaruwangway closed 11 months ago
@lauri-codes, can you please have a look at this?
We have migrated the perovskite database schemas in NOMAD to this plugin.
By doing so,
schema_sections
folder along with a couple of help function files. json.archive
files from a csv form the original perovskite database. This could have been done with the tabular parser, but that was not available back then and now it would mean adding manually 400 mapping keys. Please also add the github actions workflow that runs the tests for each commit. You can copy the config from the example repo: https://github.com/nomad-coe/nomad-schema-plugin-example/tree/main/.github/workflows
Please also add the github actions workflow that runs the tests for each commit. You can copy the config from the example repo: https://github.com/nomad-coe/nomad-schema-plugin-example/tree/main/.github/workflows
The action can not pass for now because:
one solution might be to pull the nomad repo to the testing server, and change the nomad.yml in nomad repo locally and install local package nomad to perovskite-solar-cell database, like when we test locally. Otherwise, once this plugin is included in a nomad release, the test should work here.
- nomad.datamodel.metainfo.plot only exists in nomad develop branch, so i update pyproject.toml to use develop branch as a temporarily solution
Sounds good.
- but the nomad develop branch does not change the yml file yet to include the perovskite_solar_cell package. so running test here will fail.
The main package does not need to include the plugin or the package, I think this is handled by the nomad.yaml
file in this plugin repository, which is picked when you run the tests inside the main folder? But maybe I misunderstood the problem.
closes: #1 nomad schma is originally located in the nomad source code. This PR is to make a package of perovskite solar cell plugin. so that this schema code can be removed from the nomad app code.