Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updated VLBA table

Below is a list of items that are priorities for Archive implementation, some of these are Legacy AAT retirement tickets, others are new development. The order in the tables is in priority order (aside from VLBA at the moment).


Data Delivery

Priority/Done?NotesJiRA ticket /Confluence page

Scriptable query interface

The email sent by the archive tool will include the wget command in the near future.

 

Jira
serverDMS JIRA
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7421



A friendly error is needed when a users is not authorized to access proprietary data.

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7474



Put warning that only one CMS at a time can be requested in AAT
Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7106


could be a flyover text

option to return UNTAR'd file does not work 

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-6495
https://open-confluence.nrao.edu/display/SRDP/Product+lists+for+Basic+and+Calibrated+Measurement+Set+downloads

pipeline topic

Clean up the nested directory data delivery mess


legacy VLA data deliveries are one level deeper in directories than an SDM

Delivery Directory Improvements

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7000


attempted for 4.2.0 but is deferredDon't restrict download number limit.

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7352

We would like no limit on the number of files, but keep the 10TB for the total downloaded volume.

Download weblogs directly (and/or serve them as well!)Direct weblog download from archive search return interface

Bulk download of Calibration tarballs

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7353



archive should ask for confirmation to continue if the download or processing job is considered largeTo be requestedThe front end can show size estimates for various products.

Data Delivery times out if tar file(s) are too large/time consuming


Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-6083
will not be an issue with taring not being the default.

archive-new delivery not chmod'd/chowned


Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-5096

4.1.1open up local delivery restrictions (to /home and /lustre). 

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7179

The part related to opening the download destination to nm-### accounts on lustre is

Jira
serverDMS JIRA
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7345

This should cover users with visitor accounts wanting to download data to lustre, and local staff wanting to download data to their local machines. We have a problem with the quota of the observer accounts (I downloaded 8 TB of data to my observer account!); CIS remains irresponsive!
4.1.1disable checksums by default

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7343


4.1.1make tar downloads default to 'off'

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7344


...

DMS JIRA
Priority/Done?NotesJiRA ticket /Confluence pageimport FITSAIPS files without matching projects (51 files) and project GP0024
HighAdd wget command in emails generated by the AAT upon downloading data

Jira
key,summary,type,created,updated,
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7421


HighVLBA: DA archive tools (note specifically the limitation of USNO data not having PI)

https://open-confluence.nrao.edu/display/SPR/VLBA%3A+DA+archive+tools

proprietary period setter: 

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7350

needs follow up, some things are inconsistent (especially the topic of the tool's readiness to change the proprietary period of VLBA data).
MedWrong band designation in VLBA data (old data only?)

Jira
serverDMS JIRA
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7420

This is in both the legacy archive and the new archive tool. Issue needs more research on how prevalent it is; unclear.
Med
  • For observing VLBA projects that incorporate other dishes (e.g. +Y1, +Y27 etc), the VLA files should be associated with the relevant VLBA segment and not considered as "mixed" projects. This has been descoped from ticket 
    Jira
    serverDMS JIRA
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
    keySSA-
7426
Add FITSAIPS files to new archive and segment association
  • 7185
    but needs to be picked up in future AAT releases

New JIRA ticket not yet created.
MedDefault Instrument of VLBA projects in AAT/PPI

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-
7328
7208

Confluence req: VLBA: Default Instrument of VLBA projects in AAT/PPI


LowMark4 files with 0 length getting added to new archive metadataold VLBA project metadata issues

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,
resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7379
Wrong band designation in VLBA data (old data only?)

Jira
server
resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-
7420

this is in both the legacy archive and the new archive tool.

7297

Small number of files affected.LowIncomplete VLBA data of observations crossing midnight (open in case more cases show up)

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution

Add wget command in emails generated by the AAT upon downloading data

Jira
serverDMS JIRA
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-74216916


LowCreate USNO download acknowledgementFor observing VLBA projects that incorporate other dishes (e.g. +Y1, +Y27 etc), the VLA files should be associated with the relevant VLBA segment and not considered as "mixed" projects. This has been descoped from ticket 

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution

serverIdeb2e750b-a83a-387e-8345-36eee8a98f01keySSA-7185 but needs to be picked up in future AAT releases877 VLBA correlations with missing files entries

Jira
serverDMS JIRA
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7471

VLBA data structure in the new archive - improved interface JiraserverDMS JIRA

serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-

7185

Confluence: GUI (segment hierarchy) for VLBA data in the new archive

6952


4.1.1

import FITSAIPS files without matching projects (51 files) and project GP0024

Default Instrument of VLBA projects in AAT/PPI

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a

-387e-8345-36eee8a98f01

-387e-8345-36eee8a98f01
keySSA-7426


4.1.1

Add FITSAIPS files to new archive and segment association

keySSA-7208

Confluence req: VLBA: Default Instrument of VLBA projects in AAT/PPI

VLBA: DA archive tools (note specifically the limitation of USNO data not having PI)

https://open-confluence.nrao.edu/display/SPR/VLBA%3A+DA+archive+tools

proprietary period setter: 

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
key

SSA-7350needs follow up, somethings are inconsistent (especially the topic of the tool's readiness to change the proprietary period of VLBA data).proprietary clock for VLBA data

SSA-7328


4.1.1old VLBA project metadata issues

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-

6552

7379


should have been done for 4.1.0. Stephan will follow up to confirm.1VLBA data structure in the new archive - improved interfaceVLBA Reingestion Refinements

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
DMS JIRAcolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-59177185

Confluence: GUI (segment hierarchy) for VLBA data in the new archive


877 VLBA correlations with missing files entries

Jira
serverDMS JIRA

ongoingMark4 files with 0 length getting added to new archive metadata

JiraserverDMS JIRAcolumnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolutioncolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution

serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-
7297

Small number of files affected.

7471


proprietary clock for VLBA dataIncomplete VLBA data of observations crossing midnight (open in case more cases show up)

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-69166552

doneVLBA Reingestion RefinementsCreate USNO download acknowledgement

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-

6952

5917

ongoing → done√VLBA Polarization Duplication

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-5640

done√String Terminators in VLBA fields

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-5641

done√BL473 unlock and missing segments

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7148

done√VLBA data structure in the new archive

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7076
Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7182
Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7183
Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7184

done√USNO Proprietary Download System/A way to deliver data from projects that are not archiveddone√Remove Legacy Archive label and link from new archive

Jira
serverDMS JIRA
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7375

The new archive has a link to the legacy archive at the top. This needs to be removed since the legacy archive will not be accessible from outside.

...