search

xpdAcq / mission-control

Releases, Installers, Specs, and more!
0 stars 4 forks source link

switching to "jupyter lab" instead of ipython #168

Open MehmetTopsakal opened 5 years ago

MehmetTopsakal commented 5 years ago

I think life will be much easier if we switch to "jupyter lab" (not jupyter notebook) instead of ipython terminal.

MehmetTopsakal commented 5 years ago

We can provide a template with detailed explanations for the user in the beginning of the experiment.

MehmetTopsakal commented 5 years ago

At the end of beamtime, the user exports the notebook and take it home.

MehmetTopsakal commented 5 years ago

Good to read: https://www.nature.com/articles/d41586-018-07196-1

“We went from Jupyter notebooks not existing some six years ago to in essence everybody using them today,”

sbillinge commented 5 years ago

I would place this as low priority compared to other functional needs, but Mehmet, to keep this conversation alive, please could you elaborate on what user problem, or what user use-case you would envisage that this solves? In other words, how would you envisage that users would make use of this? I get that they will take an ipynb file home, but what do they do with it when they get it home?

On Mon, Feb 25, 2019 at 12:44 PM MehmetTopsakal notifications@github.com wrote:

Good to read: https://www.nature.com/articles/d41586-018-07196-1

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/xpdAcq/mission-control/issues/168#issuecomment-467107178, or mute the thread https://github.com/notifications/unsubscribe-auth/AEDrURFFVOaxKH8psuJqcQZcqEX3JcINks5vRCDjgaJpZM4bQaJG .