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
There are currently two helioviewer servers at GSFC. Both need to be receiving new images from the JP2 generation computer. Therefore the JP2Gen generation computer needs to be able to transfer to multiple machines. Currently JP2Gen can only move data to a single machine.
I don't think this was ever completed, and it didn't meet our deadline back in May anyway. I've pretty much worked around this by adding helioviewer.org itself as a source for certain images. Mirrors can use the hv_* server definitions to pull data from helioviewer. This is how I get STEREO and SOHO data onto the beta server.
With that, we can probably close this unless you can think of a good reason for still needing it.
There are currently two helioviewer servers at GSFC. Both need to be receiving new images from the JP2 generation computer. Therefore the JP2Gen generation computer needs to be able to transfer to multiple machines. Currently JP2Gen can only move data to a single machine.
A potential solution is to change the values in the
remote
structure (https://github.com/Helioviewer-Project/jp2gen/blob/master/idl/local/EXAMPLE_hv_writtenby.pro#L52) into arrays, and then have the transfer scripthv_transfer_jp2.pro
(https://github.com/Helioviewer-Project/jp2gen/blob/master/idl/gen/hv_jp2_transfer.pro#L73) step through all the remote locations indicated in the modifiedhv_writtenby.pro
file. I think a simplefor...endfor
loop to index the remote location data should be sufficient.The text was updated successfully, but these errors were encountered: