The Analytics Engine JupyterHub is currently exclusively provided to energy sector partners in California, in alignment with funding from the California Energy Commission. While the JupyterHub platform access is limited to these users, all data, analytics, and JupyterHub notebook code are fully open source. For details on how to access the available data, visit the Accessing Data section of our website. To stay up to date on the progress of the Analytics Engine project and be added to our contact list, please send us an email.
If you have an account, please sign in to the Analytics Engine to get started.
Check out our Introduction page if you are interested in leveraging the Analytics Engine for professional services outside of our current funding scope and would like to learn more.
Server Options Available on the Analytics Engine JupyterHub
When you log into the Analytics Engine (AE) JupyterHub, you will be prompted to select a server size before starting your session. This allows users to match compute resources to their analytical needs while helping the project manage shared AWS resources efficiently.
Two server options are available:
- Small (2 CPU, 14 GB RAM): This is the recommended option for most users and most workflows. It supports standard analyses and uses fewer AWS credits.
- Medium (4 CPU, 28 GB RAM): This option is intended for larger datasets or more computationally intensive analyses. It consumes AWS credits more quickly and should only be selected when additional memory or processing power is clearly needed.
If you are unsure which option to choose, start with Small. We recommend you move to Medium only if you encounter performance limitations such as memory errors or very slow computation that cannot be resolved through more efficient analysis approaches.
Note: All users should select the Default environment when starting a server unless they have been explicitly instructed otherwise by the Analytics Engine team. The Default environment is fully supported and configured for Analytics Engine tools and workflows.