You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/playbook.rst
+13-19Lines changed: 13 additions & 19 deletions
Original file line number
Diff line number
Diff line change
@@ -228,7 +228,7 @@ The bucket ``rubin-pp-dev`` holds incoming raw images.
228
228
The bucket ``rubin-pp-dev-users`` holds:
229
229
230
230
* ``rubin-pp-dev-users/central_repo_2/`` contains the central repository described in `DMTN-219`_.
231
-
This repository currently contains HSC, LATISS, LSSTComCamSim, LSSTCam, and LSSTCam-imSim data, uploaded with ``make_export.py``.
231
+
This repository currently contains HSC, LATISS, and LSSTCam data, uploaded with ``make_export.py``.
232
232
233
233
* ``rubin-pp-dev-users/unobserved/`` contains raw files that the upload scripts can draw from to create incoming raws.
234
234
@@ -346,7 +346,7 @@ To inspect table permissions:
346
346
set search_path to <namespace>;
347
347
\dp
348
348
349
-
Most tables should grant the SELECT (r) and UPDATE (w) `PostgreSQL privileges`_ to all service users (currently ``latiss_prompt``, ``hsc_prompt``, ``lsstcam_prompt``, and ``lsstcomcamsim_prompt``).
349
+
Most tables should grant the SELECT (r) and UPDATE (w) `PostgreSQL privileges`_ to all service users (currently ``latiss_prompt``, ``hsc_prompt``, and ``lsstcam_prompt``).
350
350
Some tables also need INSERT (a) and DELETE (d).
351
351
352
352
We need SELECT (r) and USAGE (U) permissions for the sequence ``collection_seq_collection_id``, but *not* for ``dataset_calibs_*_seq_id``, ``dataset_type_seq_id``, or ``dimension_graph_key_seq_id``.
@@ -356,7 +356,7 @@ If any tables are missing permissions, run:
356
356
357
357
.. code-block:: psql
358
358
359
-
GRANT insert, select, update ON TABLE "<table1>", "<table2>" TO hsc_prompt, latiss_prompt, lsstcam_prompt, lsstcomcamsim_prompt;
359
+
GRANT insert, select, update ON TABLE "<table1>", "<table2>" TO hsc_prompt, latiss_prompt, lsstcam_prompt;
360
360
361
361
See the `GRANT command`_ for other options.
362
362
@@ -373,8 +373,8 @@ One raw was ingested, visit-defined, and kept in the development central repo, s
pipetask run -b s3://rubin-pp-dev-users/central_repo_2 -i LSSTComCamSim/raw/all,LSSTComCamSim/defaults,LSSTComCamSim/templates -o u/${USER}/add-dataset-types -d "instrument='LSSTComCamSim' and exposure=7024062700235 and detector=8" -p $AP_PIPE_DIR/pipelines/LSSTComCamSim/ApPipe.yaml -c parameters:apdb_config=apdb_config.yaml -c associateApdb:doPackageAlerts=False --register-dataset-types --init-only
377
-
pipetask run -b s3://rubin-pp-dev-users/central_repo_2 -i LSSTComCamSim/raw/all,LSSTComCamSim/defaults,LSSTComCamSim/templates -o u/${USER}/add-dataset-types -d "instrument='LSSTComCamSim' and exposure=7024062700235 and detector=8" -p $AP_PIPE_DIR/pipelines/LSSTComCamSim/SingleFrame.yaml -c parameters:apdb_config=apdb_config.yaml --register-dataset-types --init-only
376
+
pipetask run -b s3://rubin-pp-dev-users/central_repo_2 -i LSSTCam/raw/all,LSSTCam/defaults,LSSTCam/templates -o u/${USER}/add-dataset-types -d "instrument='LSSTCam' and exposure=2025050100367 and detector=30" -p $AP_PIPE_DIR/pipelines/LSSTCam/ApPipe.yaml -c parameters:apdb_config=apdb_config.yaml -c associateApdb:doPackageAlerts=False --register-dataset-types --init-only
377
+
pipetask run -b s3://rubin-pp-dev-users/central_repo_2 -i LSSTCam/raw/all,LSSTCam/defaults,LSSTCam/templates -o u/${USER}/add-dataset-types -d "instrument='LSSTCam' and exposure=2025050100367 and detector=30" -p $AP_PIPE_DIR/pipelines/LSSTCam/SingleFrame.yaml -c parameters:apdb_config=apdb_config.yaml --register-dataset-types --init-only
378
378
379
379
.. note::
380
380
@@ -528,15 +528,14 @@ Install the Prompt Processing code, and set it up before use:
528
528
The tester scripts send ``next_visit`` events for each detector via Kafka on the ``next-visit-topic`` topic.
529
529
They then upload a batch of files representing the snaps of the visit to the ``rubin-pp-dev`` S3 bucket, simulating incoming raw images.
530
530
531
-
``python/tester/upload.py``: Command line arguments are the instrument name (currently HSC, LATISS, LSSTComCamSim, LSSTCam, and LSSTCam-imSim), and the number of groups of images to send.
531
+
``python/tester/upload.py``: Command line arguments are the instrument name (currently HSC, LATISS, and LSSTCam), and the number of groups of images to send.
532
532
533
533
Sample command line:
534
534
535
535
.. code-block:: sh
536
536
537
537
python upload.py LATISS 3
538
538
python upload.py LSSTCam 5
539
-
python upload.py LSSTCam-imSim 2
540
539
541
540
This script draws images stored in the ``rubin-pp-dev-users`` bucket.
542
541
@@ -545,9 +544,7 @@ This script draws images stored in the ``rubin-pp-dev-users`` bucket.
545
544
* For LATISS, 3 groups, in total 3 raw fits files and their corresponding json metadata files, are curated.
546
545
One of the files, the unobserved group `2024-09-04T05:59:29.342`, has no templates and is known to fail `calibrateImage` in determining PSF.
547
546
This visit can test pipeline fallback features.
548
-
* For LSSTComCamSim, 2 groups, in total 18 raw fits files and their corresponding json metadata files, are curated.
549
547
* For LSSTCam, 5 groups, in total 10 raw fits files and their corresponding json metadata files, are curated.
550
-
* For LSSTCam-imSim, 2 groups, in total 3 raw fits files and custom-made json metadata files, are curated.
551
548
552
549
``python/tester/upload_from_repo.py``: Command line arguments are a configuration file, and the number of groups of images to send.
Prompt Processing is configured to ignore messages that have already been read by another consumer. To view messages statistics for a consumer group enter ``XINFO GROUPS <consumer_group_name>`` with the `Redis CLI`_. An example below with the ComCamSim consumer group. The ``lag`` is ``9`` so 9 messages have not been acknowledged. To manually clear these messages see `Clear Redis Stream`_
774
+
Prompt Processing is configured to ignore messages that have already been read by another consumer. To view messages statistics for a consumer group enter ``XINFO GROUPS <consumer_group_name>`` with the `Redis CLI`_. An example below with the LSSTCam consumer group. The ``lag`` is ``9`` so 9 messages have not been acknowledged. To manually clear these messages see `Clear Redis Stream`_
781
775
782
776
.. code-block:: sh
783
777
784
-
127.0.0.1:6379> XINFO GROUPS instrument:lsstcomcamsim
778
+
127.0.0.1:6379> XINFO GROUPS instrument:lsstcam
785
779
1) 1) "name"
786
-
2) "lsstcomcamsim_consumer_group"
780
+
2) "lsstcam_consumer_group"
787
781
3) "consumers"
788
782
4) (integer) 704
789
783
5) "pending"
@@ -799,13 +793,13 @@ In the above example there are 72 ``entries-read`` which is 72 messages acknowle
799
793
800
794
Clear Redis Stream
801
795
------------------
802
-
To delete all the events in a Redis stream the ``DEL`` command can be used. Below is an example with ComCamSim to delete and recreate the Redis Stream. Please note there will be errors generated by Keda any Scaled Jobs connected to the stream when the stream is deleted.
796
+
To delete all the events in a Redis stream the ``DEL`` command can be used. Below is an example with LSSTCam to delete and recreate the Redis Stream. Please note there will be errors generated by Keda any Scaled Jobs connected to the stream when the stream is deleted.
0 commit comments