gwastro · GarethCabournDavies · Apr 17, 2025 · Apr 18, 2025 · Apr 18, 2025 · Oct 7, 2025
diff --git a/.github/workflows/bank-compress-workflow.yml b/.github/workflows/bank-compress-workflow.yml
@@ -48,7 +48,6 @@ jobs:
         cp examples/tmpltbank/compress_workflow/*.ini ./
         bash -e examples/tmpltbank/compress_workflow/gen.sh
         cd output
-        bash -e ../examples/search/submit.sh
         python ../examples/search/check_job.py
         find submitdir/work/ -type f -name '*.tar.gz' -delete
     - name: store log files

diff --git a/.github/workflows/inference-workflow.yml b/.github/workflows/inference-workflow.yml
@@ -42,7 +42,6 @@ jobs:
         bash -e examples/workflow/inference/small_test/gen.sh
         condor_status
         cd gw_output
-        bash -e ../examples/search/submit.sh
         ./status
         python ../examples/search/check_job.py
         find submitdir/work/ -type f -name '*.tar.gz' -delete

diff --git a/.github/workflows/search-workflow.yml b/.github/workflows/search-workflow.yml
@@ -52,7 +52,6 @@ jobs:
         bash -e examples/search/gen.sh
         cp *.gwf output/
         cd output
-        bash -e ../examples/search/submit.sh
         python ../examples/search/check_job.py
         find submitdir/work/ -type f -name '*.tar.gz' -delete
     - name: store log files

diff --git a/bin/bank/pycbc_geom_aligned_bank b/bin/bank/pycbc_geom_aligned_bank
@@ -611,5 +611,4 @@ workflow += bankverify_node
 workflow.save()
 
 logging.info("GENERATION SUCCESSFUL.")
-logging.info("Submit the resulting dax file to generate your template bank.")
-logging.info("See pycbc_submit_dax --help for instructions.")
+logging.info("Submit the resulting workflow to generate your template bank.")
diff --git a/bin/pycbc_submit_dax b/bin/pycbc_submit_dax
diff --git a/docs/tmpltbank.rst b/docs/tmpltbank.rst
@@ -224,19 +224,21 @@ where ``accounting.tag`` should be replaced with one of the valid accounting
 tags. On non-LDG clusters, ``--supplement-config-file supplement.ini`` can be
 omitted if there are no extra options to give.
 
-After running ``pycbc_geom_aligned_bank``, submit the workflow with
+You can either submit the ``pycbc_geom_aligned_bank`` workflow immediately,
+using 
 
 .. code-block:: bash
 
-    pycbc_submit_dax
-
-Run
+    pycbc_geom_aligned_bank --submit-now
+
+
+or submit the workflow after generation with the 
 
 .. code-block:: bash
 
-    pycbc_submit_dax --help
+    ./start
 
-for more details on options for submitting an abstract workflow to condor.
+executable supplied in the output folder
 
 --------------------------
 Command line options

diff --git a/docs/upload_to_gracedb.rst b/docs/upload_to_gracedb.rst
@@ -25,7 +25,7 @@ You also need to be authorized on the gracedb end to do the upload. The initial
 Finding input files
 ============================
 
-To run this code requires some input files from your run. These can be found as follows where RUN_DIR is the place where you ran pycbc_submit_dax::
+To run this code requires some input files from your run. These can be found as follows where RUN_DIR is your run directory::
 
    TRIG_FILE=${RUN_DIR}/results/7._result/H1L1-PAGE_FOREGROUND_XMLLOUDEST-1130754617-1019335.xml
 

diff --git a/docs/workflow/pycbc_make_inference_inj_workflow.rst b/docs/workflow/pycbc_make_inference_inj_workflow.rst
@@ -123,21 +123,19 @@ to run the workflow.
 Plan and execute the workflow
 -----------------------------
 
-Change directory into the ``${WORKFLOW_NAME}-output`` directory::
-
-    cd ${WORKFLOW_NAME}-output
+You can either submit the workflow immediately using the ``--submit-now`` option
+or generate it, and then use the ``./start`` executable generated in the output directory.
 
 If you are on the ATLAS cluster (at AEI Hannover) or on an LDG cluster, you
 need to define an accounting group tag (talk to your cluster admins if you do
-not know what this is). Once you know what accounting-group tag to use, plan
-and submit the workflow with::
-
-    # submit workflow
-    pycbc_submit_dax --dax ${WORKFLOW_NAME}.dax \
-        --no-grid \
-        --no-create-proxy \
-        --enable-shared-filesystem \
-        --accounting-group ${ACCOUNTING_GROUP}
+not know what this is). Once you know what accounting-group tag to use, add it 
+to your config files. ``request_disk`` and ``request_memory`` may also be required.
+
+.. code-block::
+
+    [pegasus_profile]
+    condor|accounting_group = accounting.tag
+    condor|request_disk = 1024
 
 Here, ``${ACCOUNTING_GROUP}`` is the appropriate tag for your workflow.