Comments (2)
Yes, the intent was to use it to validate step config files, i.e. pars-
reffiles. Note that we used to have a datamodel called StepParsModel
back when jwst
stdatamodels
and stpipe
were all one package. When we peeled them all apart, we had to make it so that stpipe
did not depend on stdatamodels
, and hence StepParsModel
had to go.
It was removed as part of the above PR:
And since it also validated metadata, the idea was that we needed a pure ASDF schema to do the same.
The eventual goal was to completely move away from ConfigObj
as a core component of stpipe
and its configuration, and this was a step in that direction.
How do people create pars-*
reffiles these days? Just copy an old one? I suspect if they have metadata, they should be validated against this schema.
from stpipe.
Thanks for the quick response.
How do people create
pars-*
reffiles these days? Just copy an old one? I suspect if they have metadata, they should be validated against this schema.
I'm not sure about this one (and a related question is what led me to look at this schema). @hbushouse was recently providing some advice on this.
from stpipe.
Related Issues (20)
- Step.spec parsing fails when comment contains a closing parthesis
- Bundled `configobj` subject to CVE-2023-26112 HOT 3
- Failing test: ModuleNotFoundError: No module named 'roman_datamodels.tests' HOT 7
- Romancal downstream CI failing due to WebbPSF
- Making specifying a log file more convenient
- Formatting of Step parameters in log should be readable HOT 6
- The Step.get_pars() method doesn't include override_<reffile> parameters
- Support for `pathlib.Path` objects? HOT 1
- Use tmp_path instead of tmpdir pytest fixture
- Step parameters that accept path strings should accept pathlib.Path objects
- Don't allow abbreviations for long argparse options
- Step needs a parameter in spec to control output filename formatting
- Print statements always print twice
- Skipping steps while the data is in a ModelContainer causes an error
- Unable to take list-like arguments in the commandline
- Parsing step's list arguments is broken HOT 1
- strun pipeline --help doesn't list parameter defaults
- stpipe behaves weirdly with loggers HOT 3
- Move strun to project.scripts in pyproject.toml
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from stpipe.