We are working on a plan for implementing one or more alternatives to the Aspera GUI, but they are not yet in place. The HCP does not support command line access via Aspera due the version of Aspera we have. For now, we recommend mounting some part of your cluster filesystem with adequate space on a machine where you can install Aspera Connect and open a browser with the Aspera Connect plugin.
For Linux OSs we recommend using Chrome or Chromium plugins. One group reported Debian 11 with Chrome works, but they did not have success with Debian 12 or 13. This incompatibility might be due to the fact that our Aspera server has been in use for ~12 years and is aging. We should be able to get something else in place in the coming months, but we didn't want to hold up data releases when Aspera is still working for most users.
We don't have definite plans to put the HCP-YA 2025 release on AWS S3. We would need to work it out with the AWS Open Datasets program and we haven't been able to prioritize that as of yet.
The materials in this message are private and may contain Protected Healthcare Information or other information of a sensitive nature. If you are not the intended recipient, be advised that any unauthorized use, disclosure, copying or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error, please immediately notify the sender via telephone or return mail.
Hi Jenn,
Thank you for the detailed explanation. I really appreciate the context.
Understood regarding the current Aspera setup. I’ll look into whether we can temporarily mount part of our ARC filesystem onto a machine where we can install Aspera Connect with a browser, as you suggested. That’s very helpful guidance.
It’s also good to know that alternative access methods are being discussed. We'll keep an eye out for updates (If there’s any beta testing or feedback opportunity for HPC-based workflows in the future, I’d be very happy to help).
Best regards,
Tasha Kim