search

jupyterhub / mybinder.org-deploy

Deployment config files for mybinder.org
https://mybinder-sre.readthedocs.io/en/latest/index.html
BSD 3-Clause "New" or "Revised" License
76 stars 74 forks source link

COMET InSAR Workshop 2023 #2733

Closed espiritocz closed 11 months ago

espiritocz commented 12 months ago

hi everyone.

could you please bump the quotas to 300 for the next week workshop (see further), to repositories (and time) listed at point 4 below. This is related to the COMET InSAR Workshop 2023 that you kindly supported twice, see: https://github.com/jupyterhub/mybinder.org-deploy/issues/2061 and https://github.com/jupyterhub/mybinder.org-deploy/issues/2360

The current information:

  1. Who you are we are a team at the University of Leeds within UK's Centre for Observation and Modelling of Earthquakes, Volcanoes and Tectonics (COMET) - we focus particularly on satellite interferometric (InSAR) measurements of terrain deformation - we process large amounts of InSAR data and publish in open access, see our https://comet.nerc.ac.uk/COMET-LiCS-portal

  2. A few details about the event/course/context COMET InSAR Workshop used to be a popular (and competitive) live international workshop where top (UK) experts shared their knowledge about InSAR, modelling of geophysical processes, or discussed anything seismic/volcanic. We have attempted for an online form last year but faced many technical difficulties. This year, the 2 days hybrid workshop will happen on 7-8 September, in connection to the international conference ESA Fringe 2023, see: https://fringe2023.esa.int/comet-insar-training/

  3. If money is changing hands (attendees pay a fee, speaker is getting paid, free, etc) processing tools and data are available open-source (free). speakers are not financially rewarded. This year, we do not charge for the workshop, see e.g. the registration page: https://www.eventbrite.co.uk/e/comet-insar-training-workshop-2023-in-person-and-online-tickets-634561690097

  4. A link to the repository you are using The practicals using mybinder.org are using following repositories in each session:

session 1: 7th Sep 2023, 14:00-16:00 UTC: https://github.com/comet-licsar/licsbas session 2: 8th Sep 2023, 09:00-12:00 UTC: https://github.com/andwatson/coseismic_practical session 3: 8th Sep 2023, 09:00-12:00 UTC: https://github.com/andwatson/interseismic_practical session 4: 8th Sep 2023, 14:00-15:00 UTC: https://github.com/andwatson/volcano_practical session 5: 8th Sep 2023, 15:00-16:00 UTC: https://github.com/matthew-gaddes/insar_workshop

  1. What type of event it is: workshop

  2. How many people you expect to attend the event <300 (about 10 in-person and over 200 online)

  3. The exact times and dates of the event(s) (with timezone information) The event will take place on 7th and 8th September, 8:00-16:00 UTC. See point 4 for detailed schedule (relevant to mybinder.org)

  4. How do you plan to give mybinder.org a shout out at the event We add your logo to our flyer shared through our LiCS Portal website, Twitter (X) and also website of the ESA Fringe 2023 conference (see link in point 2). We will provide the logo also to some other relevant material, e.g. the logo will be visible in recorded webinars etc. We will also verbally acknowledge mybinder.org during the practical sessions. The logo is visible also during registration (see link in point 3)

Many thanks in advance for your feedback - I guess there is some time to communicate details. (related to disk space and RAM, the 2 GB RAM in your nodes and 1 GB of disk space per user should be ok, as we used this configuration last years without issues)

espiritocz commented 11 months ago

hi, could you check this please? The workshop is tomorrow + Friday... (fingers crossed)

manics commented 11 months ago

Sorry for the delay in replying, we're still limited in our available resources due to a cut in funding. We're working on finding addition cloud compute to add to the federation but that'll take a while. Even if we increased the quotas I don't think we can guarantee availability.

I haven't looked at your repos, but one option is to see if it can run on JupyterLite: https://jupyterlite.readthedocs.io/en/latest/

@minrk @rgaiacs given the short notice what do you think- is it worth increasing the quotas anyway and taking the risk that we don't have capacity?

minrk commented 11 months ago

We can bump it, but there's a high chance Binder will be full without reaching the quota anyway.

espiritocz commented 11 months ago

hi both,

thanks.. i am now checking jupyterlite but it appears it will not be enough for the repo I deal with (quite heavy, with lot of deps, something indeed for docker->binder). ok, is there a way to have one 'private' node per each repository that will 'work for sure' (for the presenter)? In case students will reach the limit, it can demonstrate need to somehow support binder community in future (I can myself ask to allocate some funds to ensure the service works, but we're now speaking about workshop tomorrow...)

cheers

st 6. 9. 2023 v 13:03 odesílatel Min RK @.***> napsal:

We can bump it, but there's a high chance Binder will be full without reaching the quota anyway.

— Reply to this email directly, view it on GitHub https://github.com/jupyterhub/mybinder.org-deploy/issues/2733#issuecomment-1708218353, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADYYKRMDV37JG7CO6TYB3TXZBRC5ANCNFSM6AAAAAA4GJYV4A . You are receiving this because you authored the thread.Message ID: @.***>

manics commented 11 months ago

We can't guarantee a node, but once a presenter has started their container then as long as it stays active it should keep running for a few hours.

An alternative is to spin up your own JupyterHub server (or BinderHub, though JupyterHub will be easier given the time pressure). For instance you could sign-up for one of the public cloud free trials/credits:

You'd need to build your singleuser environment. Ideally all dependencies across all workshops would be in the same environment to keep things easy for users, though you could also create multiple conda virtual environment and have users switch between them.

espiritocz commented 11 months ago

thanks Simon.

i am getting a local jupyterhub set at the uni, but will anyway keep using binder for the online participants (fingers crossed)

out of curiosity, are the issues you experience related to the coin miners (as was the case for pangeo binder)?

i will contact you next year to ask for update related to the next workshop. thank you for your activities, we appreciate!!!

On Wed, 6 Sep 2023, 15:51 Simon Li, @.***> wrote:

We can't guarantee a node, but once a presenter has started their container then as long as it stays active it should keep running for a few hours.

An alternative is to spin up your own JupyterHub server (or BinderHub, though JupyterHub will be easier given the time pressure). For instance you could sign-up for one of the public cloud free trials/credits:

You'd need to build your singleuser environment. Ideally all dependencies across all workshops would be in the same environment to keep things easy for users, though you could also create multiple conda virtual environment and have users switch between them.

— Reply to this email directly, view it on GitHub https://github.com/jupyterhub/mybinder.org-deploy/issues/2733#issuecomment-1708524659, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADYYKQ2ZUM7G3DYNH6A5TDXZCEW5ANCNFSM6AAAAAA4GJYV4A . You are receiving this because you authored the thread.Message ID: @.***>

manics commented 11 months ago

The capacity limit is due to the much more mundane reason of a reduction in donated cloud compute: https://blog.jupyter.org/mybinder-org-reducing-capacity-c93ccfc6413f

rgaiacs commented 11 months ago

Can we close this given that the workshop already happen?

espiritocz commented 11 months ago

dear all,

many thanks for great support! the workshop was a success, I am not aware of participants that would report issues running the lessons on your binder service.

wish you successful continuation, and happy to turn to you again next year.

please close this issue as solved

On Thu, 14 Sep 2023, 12:49 Raniere Silva, @.***> wrote:

Can we close this given that the workshop already happen?

— Reply to this email directly, view it on GitHub https://github.com/jupyterhub/mybinder.org-deploy/issues/2733#issuecomment-1719300145, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADYYKSSO2OZ2HWAF75EYIDX2LVNPANCNFSM6AAAAAA4GJYV4A . You are receiving this because you authored the thread.Message ID: @.***>