• P-series runs every other day.
• Z-Series runs approximately every three days.
  
  • BR cable/phase cal problem
    
    • Maintenance visit in late August 2023 at first seemed to have fixed the cable cal problem at BR, there was only one observation at the end of August and one in October that still had jumps in the cable cal but every other observation in September and October has looked okay. However, in November the cable cal problem began appearing again.
    • USNO reports that BR cable cal was less of an issue in March and April.
      • VLBA has noticed an increase in cable cal jumps in recent weeks. They appear to occur around the same times each day, 2000 and 0800 UT. Site tech speculates late afternoon heat and overnight cooling is causing expansion and contraction of cables.
  • SC began having a cable cal problem in June 2023. Still being investigated.
• Q-series intensive observations at MK run on weekends.
• I-series "Holiday" intensive observations at MK, substituting for Kokee on federal holidays.
  • MK will substitute for KK in regular I-series intensives for a period while a receiver replacement is made at KK (see below).

• No backlog to catch up on in June.
• A US006 that was supposed to run in May did not run until early June due to files arriving very late in May. It was not counted as backlog due to US006 previously sometimes only submitted one file a month and not using all of its requested time, so the one that did run in May was assumed to be all they had sent.
• Fifteen P-series initially requested, NRAO pre-monthly report dropped it to 13 in anticipation of HN being out for a week due to site generator install. Only ten ran due to HN being out for a second week to do an azimuth wheel bearing replacement.

• UG005 has two dissimilar sessions, one 24-hour and one 16-hour (may not observe the 16-hour session).
• Q-series request asked for ten sessions, five weekends, but there are only four weekends in July. VLBA pre-monthly report reduced it down to eight sessions and requested hours dropped by two hours.

• Nothing unusual noticed in request.

• KK will be down September 18 for six to eight weeks for a receiver replacement.
  
  • IVS would like to use MK for the Monday-Friday Int1 sessions while Kokee is down.
  • USNO will be discussing it further with Haystack and Kokee June 11.
  • VLBA data analysts expressed concern over getting the I-session files in a timely manner because they need to be manually edited before they will run on MK and in the past have often arrived on the late side.
    • This has become less of a concern due to recent changes in getting the files to VLBA.
  • VLBA scheduler expressed concern over getting 24-hour observations scheduled (USNO and open skies) as we try to avoid having them interrupted by intensives, especially multiple ones (currently the P and Q-series runs), as the 24-hour projects usually require MK. Having M-F intensives at MK would severely reduce those scheduling possibilities.
    • USNO will need to discuss the interruption situation for 24-hour projects internally.
    • Decision was that it will be okay for their 24-hour projects to be interrupted by the intensives.
  • Plan looked to be to have MK observe the I-series intensives on Tuesday and Thursdays starting September 19.
    • P-series observations most likely to be scheduled before or after those sessions on Tuesdays and Thursdays and a third weekly session on the weekends.
    • There's pressure from IVS to do more, want Monday, Tuesday and Thursday. Would run P-series on the same days. Drop Z-sessions to twice a week.
• S-band performance issues
  • RFI has been increasingly affecting S-band observations for VLBA and VLA.
  • Does anyone at USNO have time to work with NRAO on looking into this issue?
    
    • USNO will be in touch with Justin.
      • Justin's been testing things with the P-series setups.
      • Test results not promising for astronomy observations in S-band.
      • Has looked at other setups used by USNO, very similar to what's already been tested.
      • Can remove topic, pretty much done.
• Data ingest of IVS data to NRAO/Socorro in support of USNO backup correlator operations:
  • We will do a monthly test of the backup correlator by correlating a WZ-KK intensive. .
    
    • Future tests: July 10, August 14, September 4, October 1, November 6, December 4
    • July test - went okay. Note that the amount of data to download has increased due to an increase in the data rate of the intensives.
  • Further use of the backup correlator in the processing of P-series and Z-series observations has been proposed.
    • Eventual goal would be to see a demonstration of these being processed on the backup correlator without the involvement of any DC-based USNO personnel.
    • Some testing might involve using the VLBA correlator rather than the backup correlator.
    • Will be easier for VLBA to handle after the deployment of the e-transfer filesystem later in 2024.
      • etc/etd will be the only transfer software initially supported by the e-transfer system.
      • Kokee will need to be asked to change to this software for the COOP tests. Wetzell has already switched to it.
    • This will hopefully transition into the ability to do bigger projects for USNO at DSOC such as the 24-hour R4 observations.
    • Testing has been done on both P and Z series observations with the backup correlator.
      • Storage space in the datacopy areas is insufficient to hold data from a P series and a Z series at the same time.
      • Data transfer rates were exceptionally slow, probably due to using rsync because tsunami and etc/etd were not available to USNO users on gygax.
        • Will need to get USNO access to the new transfer software before further testing can be done.
        • Progress?
  • USNO would like to be able to check automatically if the backup correlator is up or down but are unable to do so, can NRAO set something up for this?
    
    • Might have to wait for e-transfer to be operational at NRAO due to internet security concerns.
      • external facing server has not been certified yet but hopefully by next month there will be news.
        • Waiting on IP addresses to be set up
          • addresses created in late May. More network stuff needs to be done?
• Replacements of the Xcubes with DBS units
  
  • Installs were completed on May 2.
  • New software will ultimately cause a change in the naming structure of data files and PFB (Mark5B) data format will no longer be supported, instead it will be converted on the fly to VDIF format.
    
    • Software changes will need further testing before deployment. First iteration of the updates may not change naming structure of data files, may also not include the PFB->VDIF format.
• Higher speed network connections to HN and MK opens the possibility of realtime correlation of intensives.
  
  • Neither Washington correlator nor NRAO set up to do it yet.
    
    • Blocking issue for NRAO is mostly network speed into the correlator. This will probably be another thing that has to wait for the e-transfer hardware to be installed.
      • There also appears to be a bottleneck at the switch into the DSOC, that may need to be upgraded too.
    • USNO made some upgrades to their correlator's networking, up to ~2.5 Gbps on an individual transfer, but still not quite fast enough to do realtime transfers. Further upgrades are being worked on - probably will have to wait for the v3 correlator. USNO is getting a new data server for e-transfer, don't know if it will provide enough overhead to allow for realtime. Might know more next month.
• Is it possible to reduce the latency on 24-hr geodetic USNO-only sessions, with a goal of a latency between the completion of observation to analyzed result under 7 days?
  • E-transfer not really practical at this time so expedited shipping of disk packs is needed.
  • Might be limited to just attempting it for one of the two observations per month.
  • Record of time to correlation:
    
    • first year of observations (UD011 AA - AR) average time was 9 days. (Specifics can be found in minutes of previous meetings.)
    • UD011 AS 9 days, UD011 AT 11 days, UD011 AU 6 days, UD011 AV 12 days, UD011 AW - 6 days, UD011 AX - 12 days, UD011 AY - 9 days, UD011 AZ - 15 days, UD011 BA - 7 days, UD011 BB - 17 days, UD011 BC - 8 days, UD011 BD - 20 days, UD011 BE - 8 days, UD011 BF - 18 days, UD011 BG - 16 days, UD011 BH - 13 days, UD011 BI - 9 days, UD011 BJ - 11 days, UD011 BK - 9 days, UD011 BL - 13 days, UD011 BM - 11 days, UD011 BN - 14 days due to a recorrlelation being necessary.
• New IVS session code naming structure change in 2024
  • On NRAO's side, the Mark6 disk pack shipping/tracking program Packtrack has some problems with lengthy project codes but there are workarounds. This would only affect any intensives which get correlated in Socorro off of disk packs, currently there are none.
    • Plans are being developed in NRAO to overhaul Packtrack to cover things such as longer project codes and e-transferred data.
    • Packtrack will need to be rewritten to work under more up-to-date versions of Linux OS before other changes can be implemented.
      • The rewrite has been postponed to FY25 due to a lack of resources.
  • IVS will continue to use the existing shorter naming structure through all of 2023 into 2024.
    
    • USNO notes they are using the longer naming structure in correlation and archiving of data but will probably hold off on using it for observations until after IVS makes the switch.
      • No firm date yet for IVS to make the switch, still working on software.
        • Might start using longer codes July 1 on some intensive observations but not all of them immediately, depends on software developments. Goal is to be fully on the new naming convention before FY25.
        • USNO doesn't think any have started using the longer names yet.
  • USNO sent some representative "new style" IVS observing codes for NRAO to run through its software looking for any unexpected problems.
    • Test NT2022224 AAA ran on Aug 12, 2022.
    • DiFX does have some project code length limitations, a modified trunk version of has been made for the correlation and the change will hopefully go into the next release (DiFX 2.8,which has now been released.)
      • There is an issue with Mark4 data, it does impact some USNO data (though not VLBA data).
      • USNO not using DiFX 2.8 yet. Also believe that 2.8 has a problem with mixed mode?
    • SCHED also has some project code length limits but SKED and VieSched ++ may not?
    • Some minor issues were found with archiving of data and some automated emails truncated the longer project code.
      • Xcube/DBS recording software does look at project codes to determine to record or not, will need to be addressed.
        • Z2024160A was observed June 8, the DBS units did not catch the longer project code name.
        • Test did run through USNO's side with no issues.
• Can some kind of acknowledgement be added to USNO data in the NRAO data archive indicating USNO's involvement?
  • Learned in mid-April that this has been pushed back to development cycle AAT 4.4.1 which is expected out in November 2024.
    
    • Walter was able to get this pushed up to AAT 4.3.2 which is expected out in August 2024.
• Possible changes coming to login accounts on DBS modules, moving to a group USNO account rather than using individual accounts?
  • No ETA on if/when group accounts would be instituted.
  • NRAO is trying to move away from group accounts for cybersecurity reasons so things may remain with individual accounts.
• USNO-NRAO contracts:
  
  • V3 DiFX (correlator upgrade) contract awarded in March 2023.
    • Biweekly build status meetings between NRAO and USNO are being held Wednesdays.
    • Some issues in installing DiFX 2.6.1 and its reliance on Python2 but it's in progress.
    • Still some issues, especially with needing some backwards compatibility with v2.5, but work continues. :

Long term issues

• Next DiFX release (2.8.2?) - a blocker issue for moving on to the next version for NRAO and probably USNO too has been resolved so moving to testing phase of the next release candidate can happen. Meetings for that began in May, probably take a couple months to sort everything out. Will be first release of it through GIT, procedures haven't been established for that yet. USNO input should be directed to Walter. August probably the earliest it could be released.
• NRAO will at some point begin doing data downloads during and after observations and this could conflict with USNO's own data downloads of the intensives.
  • Currently NRAO is only regularly doing data downloads once a week during a post-maintenance day test. Sometimes this does come shortly after a Z-series observation during the night.
    • USNO has not noticed any problems with their data downloads even when this has been the case.
  • Data downloads are also being done during the Z-series and P-series observations for realtime fringe checks, but this ends when the observation does so would not interfere with the following data downloads by USNO.
• There's interest in having VLBA observe along with a VGOS session in "mixed-mode".
  
  • First IVS needs to move some correlation off to other correlators and then they can start considering adding more stations like VLBA to the VGOS observations.
    • Not ready to include VLBA yet. Still issues within IVS and mixed mode to address first.
    • Some mixed mode issues may have been resolved.
    • Might add some VGOS stations to RDV observations to see how that works, VLBA correlator should be able to handle it
• .Peculiar delays - VLBA has a delay compared to Kokee that perhaps should be checked out, maybe put some VLBA stations into a KK observation as tagalongs so comparisons can be made. Walter reached out to some people, says it looks like it would be a bigger effort than anticipated.
  
  • Possibility of adding KK to an RDV observation raised..
    • KK will be in the April 2024 RDV observation so could get data from that.
      • RV165 observed April 24. Has been correlated.
      • After USNO (or NASA?) does analysis a copy of the clock offsets can be provided to VLBA for comparisons.
        • USNO has started analysis.
      • Kokee does have a different maser compared to last time VLBA correlated with them, might have an effect?
• Installation of new GPS receivers
  • Antennas have been installed at all VLBA sites.
  • No ETA on installation of the GPS receivers.
• USNO and IVS partners have challenges with creating VLBA-valid VEX files with the SKED and VieSched ++ software packages.
  
  • Tuning VLBA at certain frequencies requires the additional commented information, it's not found in standard VEX setups/catalogs.
  • What is the plan, if there is one, for removing the need for the additional information required by the VLBA?
    • VEX2 standard will cover the missing information for VLBA, though the scheduling software used will still need to have the right setups information.
    • Probably 2024 before VLBA might switch to using VEX2, hopefully before 2025.
    • Things are okay right now with standard USNO setups and observations, could become an issue if USNO starts using non-standard setups in new observations.
    • Some testing of VEX2 has begun at NRAO.
      • Some diagnostic observations have switched to vex2 for testing purposes.
      • Seems to be okay for some regular observing, pointing and other modes still need some work.
      • No timeline for migrating to VEX2 yet but progress is being made.

• 200 Mbps minimum at each site
• 1 Gbps at PT, KP, OV, NL. FD will be upgraded to 1 Gbps in June (done?)
• 5 Gbps at HN
• 10 Gbps at LA,MK; BR should be upgraded to 10 Gbps but something is bottlenecking it to 2.5 Gbps.
• 600 Mbps at SC (download up to 400 Mbps)