apsbits 2.0.1rc1__tar.gz → 2.0.2__tar.gz

{apsbits-2.0.1rc1 → apsbits-2.0.2}/HISTORY.rst

@@ -30,7 +30,7 @@ describe future plans.
 .. Coming release content can be gathered here.
     Some people object to publishing unreleased changes.
 
-    2.0.1
+    2.0.2
     #####
 
     release expected ?
@@ -46,6 +46,16 @@ describe future plans.
     * Bump iconfig version to 2.0.1 for the baseline addition.
     * Remove run_engine section from QS config.yml file and pin QS to 0.0.22+.
 
+2.0.1
+#####
+
+released 2026-01-13
+
+Enhancements
+------------
+
+* add support for TILED_PROFILE_NAME & TILED_PATH_NAME
+
 2.0.0 (PyPI) and 1.0.6 (repository)
 ###################################
 

{apsbits-2.0.1rc1 → apsbits-2.0.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: apsbits
-Version: 2.0.1rc1
+Version: 2.0.2
 Summary: Model of a Bluesky Data Acquisition Instrument in console, notebook, & queueserver.
 Author-email: Eric Codrea <ecodrea@anl.gov>, Pete Jemian <prjemian+instrument@gmail.com>, Rafael Vescovi <rvescovi@anl.gov>
 Maintainer-email: Eric Codrea <ecodrea@anl.gov>, Pete Jemian <prjemian+instrument@gmail.com>, Rafael Vescovi <rvescovi@anl.gov>
@@ -94,6 +94,115 @@ pip install apsbits
 
 For development please reference our documentation
 
+## Startup Architecture
+
+When a user runs `from apsbits.demo_instrument.startup import *`, the following
+import and initialization sequence executes. No module runs code on import.
+All initialization flows through `startup.py` via explicit function calls.
+
+### Module Dependency Graph
+
+Arrows show import direction. No circular imports exist.
+
+```mermaid
+graph LR
+    subgraph utils["apsbits.utils (base layer)"]
+        config_loaders
+        aps_functions
+        controls_setup
+        helper_functions --> config_loaders
+        logging_setup -.->|"inside fn"| config_loaders
+        baseline_setup --> config_loaders
+        metadata -.->|"inside fn"| apsbits_init
+        stored_dict -.->|"inside fn"| config_loaders
+        sim_creator --> helper_functions
+    end
+
+    subgraph core["apsbits.core (middle layer)"]
+        core_init["core/__init__"] --> helper_functions
+        best_effort_init --> helper_functions
+        catalog_init
+        instrument_init --> config_loaders
+        run_engine_init --> controls_setup
+        run_engine_init --> metadata
+        run_engine_init --> stored_dict
+    end
+
+    subgraph demo["demo_instrument (top layer)"]
+        startup
+        nexus_cb["callbacks/nexus"]
+        spec_cb["callbacks/spec"]
+        sim_plans --> instrument_init
+    end
+
+    subgraph api["apsbits.api"]
+        create_new_instrument
+        delete_instrument
+        run_instrument --> instrument_init
+    end
+
+    apsbits_init["apsbits/__init__"]
+
+    startup --> logging_setup
+    startup --> core_init
+    startup --> best_effort_init
+    startup --> catalog_init
+    startup --> instrument_init
+    startup --> run_engine_init
+    startup --> helper_functions
+    startup --> config_loaders
+    startup --> baseline_setup
+    startup --> aps_functions
+    startup -.->|"if enabled"| nexus_cb
+    startup -.->|"if enabled"| spec_cb
+    startup --> sim_plans
+```
+
+Solid arrows = module-level imports. Dashed arrows = conditional or function-level imports.
+
+### Initialization Sequence
+
+Everything is called explicitly by `startup.py` in this order:
+```mermaid
+graph TD
+    S["startup.py"] -->|1| A["configure_logging()"]
+    A -->|reads| A1[("logging.yml")]
+    S -->|2| B["prepare_bits()"]
+    S -->|3| C["load_config()"]
+    C -->|reads| C1[("iconfig.yml")]
+    S -->|4| D["configure_logging(extra)"]
+    D -->|reads| D1[("extra_logging.yml")]
+    S -->|5| E["init_instrument()"]
+    E -->|creates| E1["instrument, oregistry"]
+    S -->|6| F["init_bec_peaks(iconfig)"]
+    F -->|creates| F1["bec, peaks"]
+    S -->|7| G["init_catalog(iconfig)"]
+    G -->|creates| G1["cat"]
+    S -->|8| H["init_RE(iconfig, ...)"]
+    H -->|creates| H1["RE, sd"]
+    S -->|"9 (if enabled)"| I["nxwriter_init(RE, iconfig)"]
+    I -->|creates| I1["nxwriter"]
+    S -->|"10 (if enabled)"| J["init_specwriter_with_RE(RE, iconfig)"]
+    J -->|creates| J1["specwriter"]
+    S -->|11| K["make_devices(...)"]
+    K -->|reads| K1[("devices.yml")]
+    S -->|12| L["setup_baseline_stream()"]
+
+    style S fill:#fff3e0
+    style A1 fill:#f3e5f5
+    style C1 fill:#f3e5f5
+    style D1 fill:#f3e5f5
+    style K1 fill:#f3e5f5
+    style E1 fill:#c8e6c9
+    style F1 fill:#c8e6c9
+    style G1 fill:#c8e6c9
+    style H1 fill:#c8e6c9
+    style I1 fill:#c8e6c9
+    style J1 fill:#c8e6c9
+```
+
+Purple = YAML config files read from disk. Green = objects available in your session.
+
 ## Testing the apsbits base installation
 
 On an ipython console

apsbits-2.0.2/README.md

@@ -0,0 +1,147 @@
+# APSBITS: Template Package for Bluesky Instruments
+
+| PyPI | Coverage |
+| --- | --- |
+[![PyPi](https://img.shields.io/pypi/v/apsbits.svg)](https://pypi.python.org/pypi/apsbits) | [![Coverage Status](https://coveralls.io/repos/github/BCDA-APS/BITS/badge.svg?branch=main)](https://coveralls.io/github/BCDA-APS/BITS?branch=main) |
+
+BITS: **B**luesky **I**nstrument **T**emplate **S**tructure
+
+Template of a Bluesky Data Acquisition Instrument in console, notebook, &
+queueserver.
+
+## Production use of BITS
+
+Please create a bits instrument using our template repository: https://github.com/BCDA-APS/DEMO-BITS
+
+
+## Installing the BITS Package
+
+```bash
+export INSTALL_ENVIRONMENT_NAME=apsbits_env
+conda create -y -n "${INSTALL_ENVIRONMENT_NAME}" python=3.11 pyepics
+conda activate "${INSTALL_ENVIRONMENT_NAME}"
+pip install apsbits
+```
+
+For development please reference our documentation
+
+## Startup Architecture
+
+When a user runs `from apsbits.demo_instrument.startup import *`, the following
+import and initialization sequence executes. No module runs code on import.
+All initialization flows through `startup.py` via explicit function calls.
+
+### Module Dependency Graph
+
+Arrows show import direction. No circular imports exist.
+
+```mermaid
+graph LR
+    subgraph utils["apsbits.utils (base layer)"]
+        config_loaders
+        aps_functions
+        controls_setup
+        helper_functions --> config_loaders
+        logging_setup -.->|"inside fn"| config_loaders
+        baseline_setup --> config_loaders
+        metadata -.->|"inside fn"| apsbits_init
+        stored_dict -.->|"inside fn"| config_loaders
+        sim_creator --> helper_functions
+    end
+
+    subgraph core["apsbits.core (middle layer)"]
+        core_init["core/__init__"] --> helper_functions
+        best_effort_init --> helper_functions
+        catalog_init
+        instrument_init --> config_loaders
+        run_engine_init --> controls_setup
+        run_engine_init --> metadata
+        run_engine_init --> stored_dict
+    end
+
+    subgraph demo["demo_instrument (top layer)"]
+        startup
+        nexus_cb["callbacks/nexus"]
+        spec_cb["callbacks/spec"]
+        sim_plans --> instrument_init
+    end
+
+    subgraph api["apsbits.api"]
+        create_new_instrument
+        delete_instrument
+        run_instrument --> instrument_init
+    end
+
+    apsbits_init["apsbits/__init__"]
+
+    startup --> logging_setup
+    startup --> core_init
+    startup --> best_effort_init
+    startup --> catalog_init
+    startup --> instrument_init
+    startup --> run_engine_init
+    startup --> helper_functions
+    startup --> config_loaders
+    startup --> baseline_setup
+    startup --> aps_functions
+    startup -.->|"if enabled"| nexus_cb
+    startup -.->|"if enabled"| spec_cb
+    startup --> sim_plans
+```
+
+Solid arrows = module-level imports. Dashed arrows = conditional or function-level imports.
+
+### Initialization Sequence
+
+Everything is called explicitly by `startup.py` in this order:
+```mermaid
+graph TD
+    S["startup.py"] -->|1| A["configure_logging()"]
+    A -->|reads| A1[("logging.yml")]
+    S -->|2| B["prepare_bits()"]
+    S -->|3| C["load_config()"]
+    C -->|reads| C1[("iconfig.yml")]
+    S -->|4| D["configure_logging(extra)"]
+    D -->|reads| D1[("extra_logging.yml")]
+    S -->|5| E["init_instrument()"]
+    E -->|creates| E1["instrument, oregistry"]
+    S -->|6| F["init_bec_peaks(iconfig)"]
+    F -->|creates| F1["bec, peaks"]
+    S -->|7| G["init_catalog(iconfig)"]
+    G -->|creates| G1["cat"]
+    S -->|8| H["init_RE(iconfig, ...)"]
+    H -->|creates| H1["RE, sd"]
+    S -->|"9 (if enabled)"| I["nxwriter_init(RE, iconfig)"]
+    I -->|creates| I1["nxwriter"]
+    S -->|"10 (if enabled)"| J["init_specwriter_with_RE(RE, iconfig)"]
+    J -->|creates| J1["specwriter"]
+    S -->|11| K["make_devices(...)"]
+    K -->|reads| K1[("devices.yml")]
+    S -->|12| L["setup_baseline_stream()"]
+
+    style S fill:#fff3e0
+    style A1 fill:#f3e5f5
+    style C1 fill:#f3e5f5
+    style D1 fill:#f3e5f5
+    style K1 fill:#f3e5f5
+    style E1 fill:#c8e6c9
+    style F1 fill:#c8e6c9
+    style G1 fill:#c8e6c9
+    style H1 fill:#c8e6c9
+    style I1 fill:#c8e6c9
+    style J1 fill:#c8e6c9
+```
+
+Purple = YAML config files read from disk. Green = objects available in your session.
+
+## Testing the apsbits base installation
+
+On an ipython console
+
+```py
+from apsbits.demo_instrument.startup import *
+listobjects()
+RE(sim_print_plan())
+RE(sim_count_plan())
+RE(sim_rel_scan_plan())
+```

{apsbits-2.0.1rc1 → apsbits-2.0.2}/apsbits.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: apsbits
-Version: 2.0.1rc1
+Version: 2.0.2
 Summary: Model of a Bluesky Data Acquisition Instrument in console, notebook, & queueserver.
 Author-email: Eric Codrea <ecodrea@anl.gov>, Pete Jemian <prjemian+instrument@gmail.com>, Rafael Vescovi <rvescovi@anl.gov>
 Maintainer-email: Eric Codrea <ecodrea@anl.gov>, Pete Jemian <prjemian+instrument@gmail.com>, Rafael Vescovi <rvescovi@anl.gov>
@@ -94,6 +94,115 @@ pip install apsbits
 
 For development please reference our documentation
 
+## Startup Architecture
+
+When a user runs `from apsbits.demo_instrument.startup import *`, the following
+import and initialization sequence executes. No module runs code on import.
+All initialization flows through `startup.py` via explicit function calls.
+
+### Module Dependency Graph
+
+Arrows show import direction. No circular imports exist.
+
+```mermaid
+graph LR
+    subgraph utils["apsbits.utils (base layer)"]
+        config_loaders
+        aps_functions
+        controls_setup
+        helper_functions --> config_loaders
+        logging_setup -.->|"inside fn"| config_loaders
+        baseline_setup --> config_loaders
+        metadata -.->|"inside fn"| apsbits_init
+        stored_dict -.->|"inside fn"| config_loaders
+        sim_creator --> helper_functions
+    end
+
+    subgraph core["apsbits.core (middle layer)"]
+        core_init["core/__init__"] --> helper_functions
+        best_effort_init --> helper_functions
+        catalog_init
+        instrument_init --> config_loaders
+        run_engine_init --> controls_setup
+        run_engine_init --> metadata
+        run_engine_init --> stored_dict
+    end
+
+    subgraph demo["demo_instrument (top layer)"]
+        startup
+        nexus_cb["callbacks/nexus"]
+        spec_cb["callbacks/spec"]
+        sim_plans --> instrument_init
+    end
+
+    subgraph api["apsbits.api"]
+        create_new_instrument
+        delete_instrument
+        run_instrument --> instrument_init
+    end
+
+    apsbits_init["apsbits/__init__"]
+
+    startup --> logging_setup
+    startup --> core_init
+    startup --> best_effort_init
+    startup --> catalog_init
+    startup --> instrument_init
+    startup --> run_engine_init
+    startup --> helper_functions
+    startup --> config_loaders
+    startup --> baseline_setup
+    startup --> aps_functions
+    startup -.->|"if enabled"| nexus_cb
+    startup -.->|"if enabled"| spec_cb
+    startup --> sim_plans
+```
+
+Solid arrows = module-level imports. Dashed arrows = conditional or function-level imports.
+
+### Initialization Sequence
+
+Everything is called explicitly by `startup.py` in this order:
+```mermaid
+graph TD
+    S["startup.py"] -->|1| A["configure_logging()"]
+    A -->|reads| A1[("logging.yml")]
+    S -->|2| B["prepare_bits()"]
+    S -->|3| C["load_config()"]
+    C -->|reads| C1[("iconfig.yml")]
+    S -->|4| D["configure_logging(extra)"]
+    D -->|reads| D1[("extra_logging.yml")]
+    S -->|5| E["init_instrument()"]
+    E -->|creates| E1["instrument, oregistry"]
+    S -->|6| F["init_bec_peaks(iconfig)"]
+    F -->|creates| F1["bec, peaks"]
+    S -->|7| G["init_catalog(iconfig)"]
+    G -->|creates| G1["cat"]
+    S -->|8| H["init_RE(iconfig, ...)"]
+    H -->|creates| H1["RE, sd"]
+    S -->|"9 (if enabled)"| I["nxwriter_init(RE, iconfig)"]
+    I -->|creates| I1["nxwriter"]
+    S -->|"10 (if enabled)"| J["init_specwriter_with_RE(RE, iconfig)"]
+    J -->|creates| J1["specwriter"]
+    S -->|11| K["make_devices(...)"]
+    K -->|reads| K1[("devices.yml")]
+    S -->|12| L["setup_baseline_stream()"]
+
+    style S fill:#fff3e0
+    style A1 fill:#f3e5f5
+    style C1 fill:#f3e5f5
+    style D1 fill:#f3e5f5
+    style K1 fill:#f3e5f5
+    style E1 fill:#c8e6c9
+    style F1 fill:#c8e6c9
+    style G1 fill:#c8e6c9
+    style H1 fill:#c8e6c9
+    style I1 fill:#c8e6c9
+    style J1 fill:#c8e6c9
+```
+
+Purple = YAML config files read from disk. Green = objects available in your session.
+
 ## Testing the apsbits base installation
 
 On an ipython console

{apsbits-2.0.1rc1 → apsbits-2.0.2}/apsbits.egg-info/SOURCES.txt

@@ -39,6 +39,8 @@ docs/source/api/demo_instrument.rst
 docs/source/api/demo_qserver.rst
 docs/source/api/index.rst
 docs/source/api/utils.rst
+docs/source/api/generated/apsbits.api.create_new_instrument.rst
+docs/source/api/generated/apsbits.api.delete_instrument.rst
 docs/source/api/generated/apsbits.core.best_effort_init.rst
 docs/source/api/generated/apsbits.core.catalog_init.rst
 docs/source/api/generated/apsbits.core.run_engine_init.rst
@@ -51,6 +53,8 @@ docs/source/api/generated/apsbits.demo_instrument.plans.rst
 docs/source/api/generated/apsbits.demo_instrument.plans.sim_plans.rst
 docs/source/api/generated/apsbits.demo_instrument.rst
 docs/source/api/generated/apsbits.demo_instrument.startup.rst
+docs/source/api/generated/apsbits.demo_instrument.suspenders.rst
+docs/source/api/generated/apsbits.demo_instrument.utils.rst
 docs/source/api/generated/apsbits.demo_qserver.rst
 docs/source/api/generated/apsbits.utils.config_loaders.rst
 docs/source/api/generated/apsbits.utils.controls_setup.rst
@@ -88,6 +92,7 @@ src/apsbits/core/best_effort_init.py
 src/apsbits/core/catalog_init.py
 src/apsbits/core/instrument_init.py
 src/apsbits/core/run_engine_init.py
+src/apsbits/core/session_setup.py
 src/apsbits/demo_instrument/README.md
 src/apsbits/demo_instrument/__init__.py
 src/apsbits/demo_instrument/startup.py
@@ -115,8 +120,10 @@ src/apsbits/tests/test_controls_setup.py
 src/apsbits/tests/test_delete_instrument.py
 src/apsbits/tests/test_device_factories.py
 src/apsbits/tests/test_general.py
+src/apsbits/tests/test_import_purity.py
 src/apsbits/tests/test_make_devices.py
 src/apsbits/tests/test_run_instrument.py
+src/apsbits/tests/test_side_effect_fixes.py
 src/apsbits/tests/test_stored_dict.py
 src/apsbits/utils/__init__.py
 src/apsbits/utils/aps_functions.py

apsbits-2.0.2/docs/source/api/generated/apsbits.api.create_new_instrument.rst

@@ -0,0 +1,14 @@
+apsbits.api.create\_new\_instrument
+===================================
+
+.. automodule:: apsbits.api.create_new_instrument
+
+
+   .. rubric:: Functions
+
+   .. autosummary::
+
+      copy_instrument
+      create_qserver_script
+      edit_qserver_folder
+      main

apsbits-2.0.2/docs/source/api/generated/apsbits.api.delete_instrument.rst

@@ -0,0 +1,14 @@
+apsbits.api.delete\_instrument
+==============================
+
+.. automodule:: apsbits.api.delete_instrument
+
+
+   .. rubric:: Functions
+
+   .. autosummary::
+
+      delete_instrument
+      get_instrument_paths
+      main
+      validate_instrument_name

{apsbits-2.0.1rc1 → apsbits-2.0.2}/docs/source/api/generated/apsbits.demo_instrument.callbacks.demo_nexus_callback.rst

@@ -1,5 +1,5 @@
 apsbits.demo\_instrument.callbacks.demo\_nexus\_callback
-======================================================
+========================================================
 
 .. automodule:: apsbits.demo_instrument.callbacks.demo_nexus_callback
 

{apsbits-2.0.1rc1 → apsbits-2.0.2}/docs/source/api/generated/apsbits.demo_instrument.callbacks.demo_spec_callback.rst

@@ -1,13 +1,19 @@
 apsbits.demo\_instrument.callbacks.demo\_spec\_callback
-=====================================================
+=======================================================
 
 .. automodule:: apsbits.demo_instrument.callbacks.demo_spec_callback
 
 
+   .. rubric:: Module Attributes
+
+   .. autosummary::
+
+      specwriter
+
    .. rubric:: Functions
 
    .. autosummary::
 
-      spec_comment
-      newSpecFile
       init_specwriter_with_RE
+      newSpecFile
+      spec_comment

{apsbits-2.0.1rc1 → apsbits-2.0.2}/docs/source/api/generated/apsbits.demo_instrument.rst

@@ -15,3 +15,5 @@
    devices
    plans
    startup
+   suspenders
+   utils

apsbits-2.0.2/docs/source/api/generated/apsbits.demo_instrument.suspenders.rst

@@ -0,0 +1,4 @@
+apsbits.demo\_instrument.suspenders
+===================================
+
+.. automodule:: apsbits.demo_instrument.suspenders

apsbits-2.0.2/docs/source/api/generated/apsbits.demo_instrument.utils.rst

@@ -0,0 +1,4 @@
+apsbits.demo\_instrument.utils
+==============================
+
+.. automodule:: apsbits.demo_instrument.utils

{apsbits-2.0.1rc1 → apsbits-2.0.2}/docs/source/api/generated/apsbits.utils.config_loaders.rst

@@ -12,3 +12,4 @@
       load_config
       load_config_yaml
       update_config
+      validate_instrument_path

{apsbits-2.0.1rc1 → apsbits-2.0.2}/docs/source/api/generated/apsbits.utils.controls_setup.rst

@@ -4,17 +4,16 @@
 .. automodule:: apsbits.utils.controls_setup
 
 
-   .. rubric:: Module Attributes
-
-   .. autosummary::
-
-      oregistry
-
    .. rubric:: Functions
 
    .. autosummary::
 
       connect_scan_id_pv
-      epics_scan_id_source
       set_control_layer
       set_timeouts
+
+   .. rubric:: Classes
+
+   .. autosummary::
+
+      EpicsScanIdSource

{apsbits-2.0.1rc1 → apsbits-2.0.2}/docs/source/api/generated/apsbits.utils.helper_functions.rst

@@ -9,6 +9,7 @@
    .. autosummary::
 
       debug_python
+      dynamic_import
       get_xmode_level
       is_notebook
       mpl_setup

{apsbits-2.0.1rc1 → apsbits-2.0.2}/docs/source/guides/setting_iconfig.rst

@@ -1,10 +1,67 @@
 Setting up your instrument
 ================================
 
-The iconfig file is a YAML file that contains the configuration for your instrument.
-It is used to set up the instrument preferences and settings. The iconfig file is
-located in the ``configs`` directory of your instrument package. Below we go through the settings available in the iconfig file.
+The iconfig file is a YAML file that contains the configuration for your
+instrument. It is used to set up the instrument preferences and settings. The
+iconfig file is located in the ``configs`` directory of your instrument package.
+Below we go through the settings available in the iconfig file.
 
+CATALOG
+----------------
+
+A *catalog* is where the data from a bluesky *run* (documents published by the
+bluesky RunEngine) is saved.
+
+``TILED_PROFILE_NAME`` (preferred)
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Name of the Tiled profile to use.
+
+If ``TILED_PROFILE_NAME`` is set, it takes precedence over ``DATABROKER_CATALOG``.
+
+The tiled profile is a special file (see ``tiled profile --help``).  It defines
+a simple shortcut to the full Tiled server URI and API key necessary for write
+access to the catalog.  A full list of the profile names available to you
+can be obtained with the command: ``tiled profile list``.
+
+``TILED_PATH_NAME`` (optional)
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Optional *server-defined* path name provided by the Tiled server.
+
+Important notes:
+
+* ``TILED_PATH_NAME`` is a path provided by the tiled server. It is not a filesystem directory path.
+* If your server only defines the tiled catalog at ``/``, do not define ``TILED_PATH_NAME``.
+* Different Tiled server deployments may provide different path names.
+* If omitted, the Tiled server default path is used.
+* Setting ``TILED_PATH_NAME: "/"`` has been observed to cause a server error.
+  In that case, do **not** define ``TILED_PATH_NAME``.
+
+Example
+++++++++++++++
+
+Example excerpt from ``configs/iconfig.yml``:
+
+
+.. code-block:: yaml
+    :linenos:
+
+    # Preferred Tiled configuration
+    TILED_PROFILE_NAME: raw
+    # Only set this if your server requires a non-default path:
+    TILED_PATH_NAME: /raw
+
+Legacy configuration
++++++++++++++++++++++++++++++++++
+
+``DATABROKER_CATALOG`` (legacy)
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+``DATABROKER_CATALOG`` is supported for backward compatibility, but
+``TILED_PROFILE_NAME`` (and optionally ``TILED_PATH_NAME``) is preferred.
+
+If both are set, ``TILED_PROFILE_NAME`` is used.
 
 RUN_ENGINE
 -----------------------------
@@ -17,7 +74,6 @@ The ``RUN_ENGINE`` section contains the configuration for the run engine. The ru
             beamline_id: demo_instrument
             instrument_name: Most Glorious Scientific Instrument
             proposal_id: commissioning
-            databroker_catalog: *databroker_catalog
 
         ### EPICS PV to use for the `scan_id`.
         ### Default: `RE.md["scan_id"]` (not using an EPICS PV)

{apsbits-2.0.1rc1 → apsbits-2.0.2}/src/apsbits/__init__.py

@@ -2,10 +2,6 @@
 
 """Model Bluesky Data Acquisition Instrument."""
 
-from apsbits.utils.logging_setup import configure_logging
-
-configure_logging()
-
 __package__ = "apsbits"
 try:
     from setuptools_scm import get_version