Mongo client for Lutz's custom sample database

[mrakitin]

This is the issue I observed while tried to run bsui with the new environment for this cycle:

[mrakitin@xf11id-dev ~]$ BS_ENV=collection-2020-2.0rc6 bsui

Versions of DAMA software:

    - Bluesky    : v1.6.4
    - Ophyd      : v1.5.2
    - Databroker : v1.0.6

Links to Bluesky and Databroker tutorials:

    - http://nsls-ii.github.io/bluesky/tutorial.html
    - http://nsls-ii.github.io/databroker/tutorial.html

If you get lost or confused, then we want to know! We have a friendly chat channel:

    https://gitter.im/NSLS-II/DAMA

or you can file a bug to let us know where our documentation could be made more clear:

    https://github.com/NSLS-II/Bug-Reports/issues

bsui is running these commands now to start an interactive computing environment for data acquisition:
    $ conda activate collection-2020-2.0rc6
    $ ipython --profile=collection --IPCompleter.use_jedi=False

Python 3.7.7 (default, Mar 26 2020, 15:48:22)
Type 'copyright', 'credits' or 'license' for more information
IPython 7.16.1 -- An enhanced Interactive Python. Type '?' for help.

IPython profile: collection
Loading metadata history from /home/mrakitin/.config/bluesky/bluesky_history.db
environment variable BLUESKY_LOG_FILE is not set, using default log file path '/home/mrakitin/.cache/bluesky/log/bluesky.log'
environment variable BLUESKY_IPYTHON_LOG_FILE is not set, using default file path '/home/mrakitin/.cache/bluesky/log/bluesky_ipython.log'
Activating auto-logging. Current session state plus future input saved.
Filename       : /home/mrakitin/.cache/bluesky/log/bluesky_ipython.log
Mode           : append
Output logging : True
Raw input log  : False
Timestamping   : True
State          : active
Exception reporting mode: Minimal
[TerminalIPythonApp] Running file in user namespace: /home/mrakitin/.ipython/profile_collection/startup/01-chxsetup.py
[TerminalIPythonApp] Running file in user namespace: /home/mrakitin/.ipython/profile_collection/startup/02-aliases.py
[TerminalIPythonApp] Running file in user namespace: /home/mrakitin/.ipython/profile_collection/startup/10-optics.py
[TerminalIPythonApp] Running file in user namespace: /home/mrakitin/.ipython/profile_collection/startup/15-machines.py
[TerminalIPythonApp] Running file in user namespace: /home/mrakitin/.ipython/profile_collection/startup/20-area-detectors.py
[TerminalIPythonApp] Running file in user namespace: /home/mrakitin/.ipython/profile_collection/startup/25-shutter.py
[TerminalIPythonApp] Running file in user namespace: /home/mrakitin/.ipython/profile_collection/startup/26-scalers.py
[TerminalIPythonApp] Running file in user namespace: /home/mrakitin/.ipython/profile_collection/startup/30-user.py
[TerminalIPythonApp] Running file in user namespace: /home/mrakitin/.ipython/profile_collection/startup/31-syringe_pump.py
[TerminalIPythonApp] Running file in user namespace: /home/mrakitin/.ipython/profile_collection/startup/34_fash_shutter_bpm_test.py
[TerminalIPythonApp] Running file in user namespace: /home/mrakitin/.ipython/profile_collection/startup/35-detectors.py
[TerminalIPythonApp] Running file in user namespace: /home/mrakitin/.ipython/profile_collection/startup/36-commisionning.py
[TerminalIPythonApp] Running file in user namespace: /home/mrakitin/.ipython/profile_collection/startup/37-database.py
[TerminalIPythonApp] WARNING | Unknown error in handling startup files:
AttributeError: 'Registry' object has no attribute 'config'


In [1]:

[tacaswell]

The issue is that they are setting up additional connections to mongo by extracting the host from databroker.

https://github.com/NSLS-II-CHX/profile_collection/blob/7c5b549d7ec4fe1edd6265ffd350863393dc0de2/startup/37-database.py#L7-L10
https://github.com/NSLS-II-CHX/profile_collection/blob/7c5b549d7ec4fe1edd6265ffd350863393dc0de2/startup/37-database2.py#L7-L10

(not sure why it is being done twice though)

We should either just embed their mongo host in the start up file or update thing to extract this information from the new databroker. I think the first option is better because we may want to migrate their databroker mongo but not touch their beamline specific stuff.

[mrakitin]

We should either just embed their mongo host in the start up file or update thing to extract this information from the new databroker. I think the first option is better because we may want to migrate their databroker mongo but not touch their beamline specific stuff.

Thanks for investigating this, Thomas A Caswell (@tacaswell). Won't the first option override the settings we want in /etc/databroker/chx.yml?

[tacaswell]

databroker will still look at the yaml file we will still respect that. It is the CHX-specific stuff that will ignore the yml. Another option is that we could read the yaml here (but then they will have to cope with any changes we make to its schema).

[mrakitin]

Sounds good. We need a volunteer to implement that :)

[jklynch]

cli = pymongo.MongoClient("xf11id-ca") 

[mrakitin]

That's easy. I wonder if we can still get it consistently from db.v1 and db.v2...

[jklynch]

I asked Dan Allan (@danielballan) and the short answer is "no".

[danielballan]

We ended up rely on private API (db.v2._run_start_collection.database.client). jklynch's approach might have been better though, so I have renamed this issue and I will leave it open as a reminder to change it.