Wrong WCS being archived when applying updatewcs with use_db=True multiple times about stwcs HOT 4 CLOSED

I think this is by design. However, I am not sure it's correct either. It works like this:

• First run
  • Run updatewcs using the distortion files and create a Primary WCS.
    WCSNAME is set to IDC_<idcfile_rootname>.
  • Get the best solution from the database. Compare it WCSNAME with the WCSNAME of the Primary one.
    If different continue (see below why they are always different)
  • Archive the Primary WCS (wcskey=A)
  • Replace the Primary WCS with the one from the database.
    WCSNAME is set to the WCSNAME of the database solution which follows a different pattern.
  • Update the distortion files with the ones used by the database solution
• Second run
  1. Run updatewcs using the distortion files (the new ones) and create a Primary WCS.
     This will use the name of the new idcfile to create a WCSNAME using the pattern IDC_<idcfile_rootname>.
  2. Get the best solution from the database (note that it is the same one as before)
  3. Archive the Primary WCS (from distortion files, wcskey=B)
  4. Compare the best solution WCSNAME with the current WCSNAME of the Primary WCS.
     Although it's the same solution the wcsnames are different because of i) above
  5. Replace the Primary WCS with the one from the database
  6. Update the distortion files with the ones used by the database solution

and so on ...

from stwcs.

Inserting a verification that the wname is unique (not already an alt WCS) before

from stwcs.

This can now be closed?

from stwcs.

Yes

from stwcs.