We currently handle HJD conversion for additive loads for this scenario:
What about additive loads of file-based formats only where one or more of which are HJD based? Either the RA/Dec must be requested via dialog or obtained from one of the files. CSS has RA/Dec info, but it seems to differ per observation (!). ASAS has RA/Dec info also, but it differs per dataset. So, one can't just say: based upon the AID data I loaded, now that I am loading an ASAS/CSS file, I can apply the same RA/Dec to all AID observations for HJD conversion purposes.
How to solve this in a general way?
As part of this, AID additive load should be possible. The current approach should work once this is enabled.
See also:
If we eventually want to move to J2000 coordinates, e.g. with a web GET version of VSX info source code, some of the links above may help.
Re: the RA/Dec dialog to be implemented when StarInfo object has null RA and Dec values:
The RA/Dec dialog will be called in Mediator.convertObsToHJD() when RA/Dec null. It should accept H|D:M:S.n or H|D.n
Observation retriever classes should specialise the base getStarInfo() method to add RA and Dec if known.
Added RA and Dec dialogs for non-AID loads in 2.16.2
See Sebastian's comment about the need for arbitrary HJD conversion:
http://www.aavso.org/naming-series-and-period-decimal-places#comment-10405
See also https://sourceforge.net/p/vstar/bugs-and-features/456/
Handled in 2.21.0. See #595.