Sergei Bolotin

Hi Eskil, The files are available on the following link: https://cddis.nasa.gov/archive/vlbi/gsfc/ancillary/solve_apriori/ On Thu, Feb 18, 2021 at 8:02 AM Eskil Varenius varenius@users.sourceforge.net wrote: [tickets:#9] https://sourceforge.net/p/nusolve/tickets/9/ Ancillary data URL not working?* Status: open Milestone: 1.0 Created: Thu Feb 18, 2021 01:02 PM UTC by Eskil Varenius Last Updated: Thu Feb 18, 2021 01:02 PM UTC Owner: nobody In nuSolve 0.7.2 UserGuide page 8 it is stated that (at time...

No. VlbiDelayType is a type, like int, char or enum, that can get the values from the table. useDelayType is a member of "config" object. This member is of type "VlbiDelayType". So it is ok to write config.useDelayType = CFG.VD_SB_DELAY, or something like that. The table 8.2 lists members of CFG (they are called "properties" as in Java script) and their types.

Eskil, nuSolve uses tools that are provided by Qt, it cannot control the implementation. There is a chance that directory or file format could change in the future. That is why it is not documented in the user guide. Well, in general, nuSolve is a GUI application, therefore all configurations are made through GUI. Yes, sometimes a user needs to change many parameters to make some specific task -- to simplify it he/she can use an alternate config ("-a" option). In a script mode it is possible to alter...

Eskil, "useDelayType" is a member of "config", it can take values of type "VlbiDelayType" which are VD_NONE, VD_SB_DELAY, VD_GRP_DELAY and VD_PHS_DELAY (as they are listed in the table). So, you can write in a script: config.useDelayType = CFG.VD_GRP_DELAY or config.useDelayType = CFG.VD_SB_DELAY and so on.

nuSolve (as well as other utilities) uses Qt's QSettings class. Qt stores the settings in ~/.config directory (~/.config/NASA GSFC/ for nuSolve and other utilities). However, the specifications of these files are not documented -- the applications have GUI to modify configuration by a user, so I feel free to change variable names and meanings of the assigned values.

Eskil, several options intentionally are reset after a session has been read. If you want to restore previous state, you should set up in Preferences "State and intermediate results autosave mode", then, when you open unsaved session, all options will be restored.

Fixed.

Hi Eskil, It is ok, do not worry :). And, please, keep asking if something happens not as expected. Kindly yours, Sergei. On Thu, Nov 5, 2020 at 9:27 AM Eskil Varenius varenius@users.sourceforge.net wrote: Oh, silly me! Well spotted. The second flag should be "-r OSO" and not "-d OSO". I missed that :(. My bad, apologies for taking your time. Please close this ticket. Kind regards Eskil [tickets:#8] https://sourceforge.net/p/nusolve/tickets/8/ -d flag should override masterfile?* Status: open Milestone:...