Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Create a class to represent visibilities / visibility data #4
The current SolarSoft/IDL structure is shown below, it will probably be necessary to keep the same fields but each visibility reproduces the entire structure. Certain elements will be the same for a group or set of visibilities such as erange, trange, xyoffset while other elements vary so could be encoded as numpy arrays (u, v, obsvis, ...).
Also some elements are specific to certain instruments (RHESSI) and may not be meaningful/usefull in general.
We need to carry the same information as in the IDL code so I think keep the names or similar names. They don't need to be arrays they should be the same for a set of visibility the only arrays should the ones we already have so use that as a base class.