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
There is several red lined sentence in OI-Interface.pdf generated by \oops command in OI-Interface.tex.
I assume that corresponds to some ideas not completely settled. Can you reread these few sentences to decide if we should keep it in the definitive version?
My idea is to have a well defined specifications written in OI-Interface.pdf before moving toward adding new algorithms.
The text was updated successfully, but these errors were encountered:
On the question of whether all of the input parameters are mandatory (first \oops in Table 1 caption) I think the following could safely be optional:
TARGET (default: assume the first target; warn if there is more than one)
FLUX (default 1)
Note that bsmem doesn't support the stated default for FLUXERR (strict constraint).
I think that any optional parameters must have the same default value regardless of which algorithm is used.
Also, there are parameters that won't be used in certain situations - for example RGL_WGT should be omitted if AUTO_WGT is true. We should spell out these contraints in the document.
I suggest to, as always, use an external tool such as OIExplorer to filter out multiple insnames. before using OImaging.
Wisard knows about insnames, because it needs to find their respective OI_WAVELENGTHs to fill up the output file. But at the moment it uses whatever V2 and T3 it finds in the file, so will use both SC and FT values for GRAVITY, which is, eh, suboptimal.
There is several red lined sentence in OI-Interface.pdf generated by
\oops
command in OI-Interface.tex.I assume that corresponds to some ideas not completely settled. Can you reread these few sentences to decide if we should keep it in the definitive version?
My idea is to have a well defined specifications written in OI-Interface.pdf before moving toward adding new algorithms.
The text was updated successfully, but these errors were encountered: