You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As discussed with Jan-Willem, the MSv4 originally was meant to contain data for only one Field
such that multi-field MSs would need to be stored in several MSv4 inside one Processing Set.
Later the MSv4 was modified to permit more than one Field.
So, for mosaics, i.e. observations of the same target with the same array in one execution block
sequentially moving over a set of Fields (in the ASDM and MSv2, they all have the same Field Name
but not the same Field ID), the questions are:
Do the data belonging to the many fields (potentially hundreds) of the same mosaic all get stored
in one MSv4 or do they get spread over many MSv4s?
What should be the default behaviour?
How can a piece of software reading the data recognise that it is dealing with a Mosaic?
How can the reading software determine the extend of the Mosaic (total number of fields, spatial extent)?
In other words, how is the metadata of the mosaic set in the first place and then made available?
The text was updated successfully, but these errors were encountered:
As discussed with Jan-Willem, the MSv4 originally was meant to contain data for only one Field
such that multi-field MSs would need to be stored in several MSv4 inside one Processing Set.
Later the MSv4 was modified to permit more than one Field.
So, for mosaics, i.e. observations of the same target with the same array in one execution block
sequentially moving over a set of Fields (in the ASDM and MSv2, they all have the same Field Name
but not the same Field ID), the questions are:
in one MSv4 or do they get spread over many MSv4s?
What should be the default behaviour?
In other words, how is the metadata of the mosaic set in the first place and then made available?
The text was updated successfully, but these errors were encountered: