Skip to content
This repository has been archived by the owner on Sep 18, 2023. It is now read-only.

Update installation instructions to current practice #119

Open
prjemian opened this issue Jul 12, 2022 · 5 comments · May be fixed by #120
Open

Update installation instructions to current practice #119

prjemian opened this issue Jul 12, 2022 · 5 comments · May be fixed by #120
Assignees
@prjemian
Labels
documentation

Comments

@prjemian
Copy link
Contributor

prjemian commented Jul 12, 2022 •
edited
Loading

Time to update the installer script. What it says now is out-of-date:

use_bluesky/install/install_startup.sh

Lines 4 to 7 in 288aa90

# purpose:
# install Bluesky IPython startup directory
# with default instrument package into `pwd`
# (within a IPython profile directory).

Now using a directory layout like this one:

~/
  bin/
    blueskyStarter.sh  --> ~/bluesky/blueskyStarter.sh
  bluesky/
    blueskyStarter.sh
    console/
      __start_bluesky_instrument__.py
    instrument/
  .ipython-bluesky/
    profile_bluesky/
      startup/
        __start_bluesky_instrument__.py --> ~/bluesky/console/__start_bluesky_instrument__.py

and __start_bluesky_instrument__.py contains:

"""
start bluesky in IPython session
"""

# start a Bluesky data collection console session
import pathlib, sys
sys.path.append(str(pathlib.Path.home()))

# terse error dumps
get_ipython().run_line_magic('xmode', 'Minimal')

from instrument.collection import *
@prjemian prjemian self-assigned this Jul 12, 2022
@prjemian
Copy link
Contributor Author

@mdwyman Thanks for the incentive.

@prjemian
Copy link
Contributor Author

Deposit the __start_bluesky_instrument__.py file into https://github.com/BCDA-APS/bluesky_training/tree/main/bluesky/resources

It should not go into the parent directory since that directory must remain compatible with the bluesky-queueserver and have only one .py file.

prjemian added a commit to BCDA-APS/bluesky_training that referenced this issue Jul 12, 2022
@prjemian
ENH BCDA-APS/use_bluesky#119
6ccfb95
prjemian added a commit that referenced this issue Jul 12, 2022
@prjemian
MNT #119 remove installation shell script
bc96542
@prjemian prjemian linked a pull request Jul 12, 2022 that will close this issue
Open
@prjemian
Copy link
Contributor Author

Also, update the instrument_package_guide.md file to include use and maintenance of instrument/iconfig.yml.

prjemian added a commit that referenced this issue Jul 12, 2022
@prjemian
DOC #119 resolve fixme items
1ae2213
prjemian added a commit that referenced this issue Jul 12, 2022
@prjemian
DOC #119 describe & demo iconfig.yml
066afc4
prjemian added a commit that referenced this issue Jul 12, 2022
@prjemian
MNT #119
263c06c
@mdwyman
Copy link
Contributor

mdwyman commented Sep 20, 2022

@prjemian I worked through the new install instructions but early on had to use micromamba instead of conda on the install bluesky environment step (https://github.com/BCDA-APS/use_bluesky/tree/119-update-install-advice/install#install-bluesky-environment). If conda was going to "solve" the environment, it would have taken >30 min (I stopped after this much elapsed). I found the micromamba instructions in the yaml file comments and it seemed to finish in <5 min. Are we moving away from conda? Should we make this explicit?

I was doing this from the APS network on beamline machines and a BC machine -- none of the conda environments were solved within 30 min. I tried several of the environments (2021_2, 2022_1, 2022_2, 2022_3) to same effect

@prjemian
Copy link
Contributor Author

prjemian commented Sep 20, 2022 via email

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@prjemian prjemian

Labels
documentation
Projects
No open projects
BDP controls preparation
Status: In Progress
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

update installation instructions to current practice BCDA-APS/use_bluesky
2 participants
@prjemian @mdwyman