Software development environment

[williamColocho]

Streamlining Simulacrum

(Top Six submitted by Greg, rest added by William)

1. Escalate simulacrum to a full part of the “dev” and “prod” environment so we have “dev”, “simul” and “prod” - While tightening up dev too.
   I’d like, when one logs into mcc-simul, you would immediately be right in the public simulator environment - like MCCDEV. Ie a cleaned up /afs/slac/g/ad/simul/ENV should executed by /etc/bash_profile. (dev and prod should also get this turn-key treatment)

2. As a consequence of 1 above - complete the sw development process as dev - simul - prod. Create cvs2dev, cv2simul, cvs2prod and git equivalents. Write the consequent sw development guide

3. (minor) Clean up the initialization scripts and instructions w.r.t. what’s executable. We have a non-executable script, use_private_simulator_data.bash, being run as an executable with an argument

4. Fix system management of private simulators. Zombie simulators cause v confusing results

5. Fix MEME services broken in private simulator. So can’t use the directory service for instance, and consequently can’t develop and test GUIs that might use those services

6. Write and publish how to use the public simulacrum from home matlab.

7. EPICS 7 PVs - Port management needed so that private simulator environment does not read public PV

8. Tools for discovering multiple private instances that may be using same EPICS ports (Duplicate PV error)

9. Create a way to view service's logs, simplify viewing public instance's logs

10. Create EDM or PyDm Simulacrum Home for user control of service restart, show logs,