Ensure Fornax has a suitable environment for OpenUniverse webinar

[troyraen]

Test the notebooks we'll use in OpenUniverse webinar using the irsa-tutorials kernel on Fornax. Complete anything needed to make them work in a user-friendly way.

Note that we removed fsps from our requirements file in #347, meaning it will be removed from the Fornax env as soon as that gets rebuilt (ie, before the workshop). It's not needed by default, but will be when users change RUN_FITS to True in SED notebook (which we should support for this webinar).

[bsipocz]

Test the notebooks we'll use in OpenUniverse webinar using the irsa-tutorials kernel on Fornax. Complete anything needed to make them work in a user-friendly way.

I think we'll need to start thinking having multiple irsa-tutorials kernel on fornax. E.g. having an fsps supporting kernel would be great, so the users can easily try it and run the notebooks with it enabled. However, it will need to be limited to python3.12, at least for a while, but I see no reason to keep that as a limit for all of the tutorials (and I foresee that as some point out other dependencies will have a 3.13+ minimum requirement so they will be mutually incompatible).

ping @zoghbi-a to see what the preference would be for multiple environments? Shall we start using multiple requirements files here, too with the premise that most of the notebooks will be compatible with the generic one, but there will be a couple of odd-ball cases?

[zoghbi-a]

If it is one package in a notebook or two, it is best to install it on the spot with pip. Any new environment we add brings with it ~0.5-1GB extra storage. If it is only the python version, we can up that to 3.13 to the irsa tutorials if needed.

The is some nuance however in that the kernels need to be added in each notebook, and py- needs to be added to the name so they don't clutter the Jupyterlab launcher, but we can work that out.

[bsipocz]

@zoghbi-a - the issue here is that it's a more complicated install and involves non-Python dependencies. So in our view it's more similar to some of the high energy tools. It's not required for all the notebooks but it's specialized software for a few use cases.

(as for python 3.13, the issue was the opposite, it didn't yet support it, but there was a release last week so the python version won't be an issue and can stay or be updated)

[zoghbi-a]

Would building it and making it available in the irsa environment do the job? Similar to what we do for tractor in one of the fornax notebooks.

[bsipocz]

you mean as a different kernel? If yes, then that should work. While with its new release it may be fully compatible with the rest of the requirements we already have use cases in the work that won't be, so I think we should be planning on eventually having a few different kernels.

[zoghbi-a]

From my side, the smaller the number of kernels the better. Currently, we have 2, and if there are really good reasons for more, we can do it.

[bsipocz]

I agree with the "as few as possible", I just fear that having just 1 won't be enough eventually.

[bsipocz]

I'm away at a conference this week, but will try to come up with a set of new configs for this and the spherex notebooks by the end of the month.