New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a class to represent visibilities / visibility data #4

Closed
samaloney opened this Issue Jul 3, 2017 · 4 comments

Comments

Projects
None yet
2 participants
@samaloney
Collaborator

samaloney commented Jul 3, 2017

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.

;  ;    IDL> help, va,/st
;  ;    ** Structure HSI_VIS, 15 tags, length=112, data length=102:
;  ;    ISC             INT              0								<- related to the grid/detector
;  ;    HARM            INT              1								<- harmonic used
;  ;    ERANGE          FLOAT     Array[2]							<- energy range
;  ;    TRANGE          DOUBLE    Array[2]						<- time range
;  ;    U               FLOAT          0.220757							<- u coordinate in Fourier space
;  ;    V               FLOAT         0.0105845						<- v coordinate in Fourier space
;  ;    OBSVIS          COMPLEX   (      7.28559,      11.1368)			<- complex Fourier component
;  ;    TOTFLUX         FLOAT          0.000000						<- total flux
;  ;    SIGAMP          FLOAT           245.240						<- simga or error on visibility
;  ;    CHI2            FLOAT           1.00000						<- chi squared from fit
;  ;    XYOFFSET        FLOAT     Array[2]						<- off set from Sun centre
;  ;    TYPE            STRING    'photon'							<- count, photon, electron
;  ;    UNITS           STRING    'Photons cm!u-2!n s!u-1!n'			<- units
;  ;    ATTEN_STATE     INT              1							<- state of the attenuator
;  ;    COUNT           FLOAT           10764.4						<- detector counts
@samaloney

This comment has been minimized.

Show comment
Hide comment
@samaloney

samaloney Aug 16, 2017

Collaborator

So we have a basic class now need to sub class to support extra info

Collaborator

samaloney commented Aug 16, 2017

So we have a basic class now need to sub class to support extra info

@pgabor

This comment has been minimized.

Show comment
Hide comment
@pgabor

pgabor Aug 18, 2017

Collaborator

Should we stay with the idl provided names or improvise based on the documentation?

Collaborator

pgabor commented Aug 18, 2017

Should we stay with the idl provided names or improvise based on the documentation?

@samaloney

This comment has been minimized.

Show comment
Hide comment
@samaloney

samaloney Aug 18, 2017

Collaborator

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.

Collaborator

samaloney commented Aug 18, 2017

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.

@pgabor

This comment has been minimized.

Show comment
Hide comment
@pgabor

pgabor Aug 18, 2017

Collaborator

Fair enough :)

Collaborator

pgabor commented Aug 18, 2017

Fair enough :)

@samaloney samaloney closed this Sep 15, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment