The Fornax Community Forum fosters collaboration and knowledge-sharing among Fornax users. Members can get help, engage in discussions, ask questions, share ideas, and collaborate on topics such as data integration, cloud computing tools, astrophysics analysis, and more.
The forum has three categories that serve different purposes:
Announcements: Learn about new features, changes, and other important information.
Helpdesk: Ask questions, report issues, request features, and get help from the Fornax team and the wider community. See Helpdesk.
User Discussion: Share insights and engage in collaborative discussions about using NASA Astrophysics mission data and Fornax resources for scientific research.
To post on the forum, you will need a Fornax account. The forum can be read without an account.
Helpdesk¶
To get support from Fornax staff, request a new feature, or report a bug, please open a topic in the Helpdesk category of the Community Forum:
You will need a Fornax account to post on the Helpdesk.
If you are having trouble logging in to your account, you don’t have an account, or you need to contact us privately, please email us at fornax
Request a large, temporary storage space
You can now manage your own scratch storage space directly from the Fornax Dashboard! Scratch storage is a working area for large data in cases where your S3 storage isn’t performant enough and your home directory is too small. You can expand your scratch area up to 3 TB for days or weeks at a time while you process large data and release it when you’re done. See Temporary Scratch Space for details.
Submit an effective bug report for Fornax
To help us quickly diagnose and resolve any issues you’re experiencing, please provide as much of the following information as possible when submitting a bug report.
Location within Fornax where the issue occurred. For example, “the JupyterLab Dask extension”.
Actions you were performing and any relevant context. For example, “running a notebook in the
python3kernel on a Medium server type”. If the issue involves a notebook or code, include a link to the exact version you were using, if possible.Expected behavior. What you anticipated would happen.
Observed behavior. What actually happened. Screenshots are helpful. If error messages, logs, or tracebacks were generated, include them in full.
Steps-by-step instructions to reproduce the problem.
Date and time (with timezone) when the issue occurred.
Web browser (name and version) you were using. For example, “Chrome 125.0.64422.142”.
Any additional information that might help. For example, if you successfully completed the same task on a previous occasion, including the date and time.
Providing detailed information will help us resolve your issue more efficiently. Thank you!