SSEC forums

I had no problem with the download - other than that it took half an hour. Perhaps you could provide the test data separate from the installation in the final product.

Some users run their web browser locally, but need to download to a larger disk on another system. For them, you may want to post the wget command on the wiki page:
https://jpss-adl-wiki.ssec.wisc.edu/med ... /Downloads

This would also allow better download resource management. I nearly brought my system to a halt by clicking on all 4 "disk" links before I realized how big they are.

gfireman wrote:I had no problem with the download - other than that it took half an hour. Perhaps you could provide the test data separate from the installation in the final product.

Only half an hour! Maybe it's a lot better now that its been a few days, but last week it took a couple overnights to get it.

I definitely recommend splitting the data sets out into a separate download. How about separate downloads for the source and then also separately for the data for the different sensors. For example, does the ATMS team really need all of the VIIRS data?

The team at RAYTHEON is working on separating code and data. The data will probably be further split up by sensor. However any way you split it VIIRS still requires a lot of input data.

My Internet connection is slow, so each file takes roughly 2.5 hours to download. Plus, I can't connect via the internet from the machines I actually do my work on, which means I then have to transfer the downloaded files to the actual machine I work on -- so double the transfer time. If I could retrieve the files via ftp then I could do it directly from the machines I do my work on which would expedite the process.