Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Developing applications on your local machine is strongly recommended as it saves on headaches with using shared OPIs and allows for robust testing on a simulated machine before launching in production.

Info
This tutorial guide was built written for unix machines, so if you have windows, you should consider setting up WSL through SLAC IT if you don't want to figure out the equivalent windows commands. if you don't want to do that, SLAC offers NoMachine as an option for running Linux, Stanford offers a virtual desktop that runs macOS, or you can install your own ubuntu in virtualbox.

...

  1. Make a GitHub account and record your username (personal or work email is fine)
  2. Add your ssh key to your GitHub account
  3. Navigate to the #comp-general Slack channel 
  4. Create a SLAC GitHub access workflow (the + with the lightning bolt at the bottomWorkflow button at the top near the channel name). An admin will review and grant you access
    1. Image Removed
    2. Image RemovedImage Added


Info
titleARM Macs

Note for anyone using ARM Macs: prefix any conda command in the following sections with CONDA_SUBDIR=osx-64 because the current builds do not support ARM. For example, instead of conda install use CONDA_SUBDIR=osx-64 conda install 

...

  1. Run conda install --update-all --force-reinstall -y -c conda-forge bmad
  2. Run git clone git@github.com:slaclab/lcls-lattice.git
    1. This repo can live wherever, just remember where it lives
    2. You may need to request access
  3. Set the LCLS_LATTICE environment variable to wherever the repo in step 2 lives
  4. Run git clone git@github.com:slaclab/simulacrum.git and remember where it lives
  5. Navigate to the newly cloned simulacrum repo and run pip install . 
  6. Run python <service directory>/<service>.py for any service you want running
    1. This will eat a terminal tab. I strongly advise against backgrounding because you'll need to kill the process eventually, and if you background it you'll either need to remember the process ID or find it later

    2. For SRF work specifically, we typically only need the sc_rf_service so the command would be python sc_rf_service/sc_rf_service.py
      1. All other services typically need the model service running with the appropriate beam line flag (python model_service/model_service.py [lcls classic | cu_hxr | cu_spec | cu_sxr | sc_hxr | sc_sxr])

...

Once you're happy with whatever program you're working on and think that it's ready (and safe) to run on production, you can connect your GitHub repo

Setup

  1. Add your AFS ssh key to github
  2. ssh into srv01 (ssh [username]@centos7.slac.stanford.edu > ssh mcclogin > ssh physics@lcls-srv01 ) and activate your own profile
  3. make a directory with the desired name (this isn't a clone so it doesn't make the directory for you)
  4. navigate to that directory and run git init
  5. run ~/zacarias/utils/linkRepoToGithub/link_repo_to_github.sh -i and follow the prompts
  6. run git pull origin main and all of the files should now be there

...