Comments (2)
analysis: the more general concept here is that an observation may acquire data about many targets and data for individual targets could be extracted into separate products (planes)... In addition to ALMA data, this seems directly applicable to instruments like multi-object spectrograph and indirectly supports various re-packaging of data based on detected features (objects, spectral features, etc).
Having target in two places in the model and usable for data discovery queries is probably going to be confusing and make for extra ugly queries so it seems better to eventually move target. We could add target to plane and deprecate Observation.target and document that the latter is only used when Plane.target is null.
By itself, adding optional Plane.target would not invalidate any existing metaChecksum values. Moving target from Observation to Plane would invalidate metaChecksums (requires re-ingest).
from caom2.
The change of CompositeObservation to DerivedObservation provides an alt pattern for this use case.
from caom2.
Related Issues (20)
- invalid combination of naxis values in Chunk passes WCS validation HOT 2
- SUBARU artifact resolution has invalid hostname
- allow hierarchy of composite observations HOT 3
- enhance position bounds to include coverage up to all-sky HOT 4
- support alternative representations of plane metadata HOT 2
- caom2-compute doesn't recognise CTYPEs: FDEP or RM HOT 6
- change Status and Quality to vocabularies HOT 2
- support range of values for plane*resolution HOT 1
- generalise CompositeObservation concept to DerivedObservation
- Add s/n (signal to noise) to Plane.Metrics HOT 6
- add Range subclass of Shape to conform to DAL standards HOT 1
- Schema description should include units. HOT 7
- CutoutUtil.initCutout in caom2-compute does not implement correct axis order HOT 1
- caom2-compute: chunk validation failure for naxis = null HOT 1
- NOAO target URL needs updating
- fits2caom2 unit tests have system-dependent Date assertions
- SUBARU resolver URL encodes the necessary query parameter HOT 2
- caom2-compute: WCS validator should check for restfrq|restwav if spectral axis is velocity
- Artifact.uri referring to a table in a TAP service HOT 2
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 caom2.