You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the current fiberassign-on-the-fly operations mode, the exposure table hyperlinks to fiberassign-??????.png plots generally give 404 errors until the day following the observations when the relevant images are copied to Berkeley. It would be nice if these fiberassign-??????.png links worked for observers in real-time. Perhaps this could be made to work with NOIRLab links that are available in real-time for an observer within the VPN. From David Schlegel on Slack:
"In general, those images won’t exist at that location until the following day since we’ve switched to fiberassign-on-the-fly (unless it’s a tile that started observation a previous night). The only location those exist will be at KPNO in the directory /data/tiles/SVN_tiles . Presumably, those files could be exposed to someone who’s on the NOIRLab VPN… but I’m not sure what to do for a more general solution."
The text was updated successfully, but these errors were encountered:
With the current fiberassign-on-the-fly operations mode, the exposure table hyperlinks to fiberassign-??????.png plots generally give 404 errors until the day following the observations when the relevant images are copied to Berkeley. It would be nice if these fiberassign-??????.png links worked for observers in real-time. Perhaps this could be made to work with NOIRLab links that are available in real-time for an observer within the VPN. From David Schlegel on Slack:
"In general, those images won’t exist at that location until the following day since we’ve switched to fiberassign-on-the-fly (unless it’s a tile that started observation a previous night). The only location those exist will be at KPNO in the directory /data/tiles/SVN_tiles . Presumably, those files could be exposed to someone who’s on the NOIRLab VPN… but I’m not sure what to do for a more general solution."
The text was updated successfully, but these errors were encountered: