ufs-community · christinaholtNOAA · Sep 11, 2025 · Sep 9, 2025 · Sep 9, 2025 · Sep 9, 2025
@@ -20,6 +20,8 @@ Positional arguments:
       The field_table file
     files_copied
       Files copied for run
+    files_hardlinked
+      Files hardlinked for run
     files_linked
       Files linked for run
     model_configure

@@ -16,6 +16,8 @@ Positional arguments:
       The executable's YAML configuration file
     files_copied
       Files copied for run
+    files_hardlinked
+      Files hardlinked for run
     files_linked
       Files linked for run
     provisioned_rundir

@@ -16,6 +16,8 @@ Positional arguments:
       The executable's YAML configuration file
     files_copied
       Files copied for run
+    files_hardlinked
+      Files hardlinked for run
     files_linked
       Files linked for run
     provisioned_rundir

@@ -16,6 +16,8 @@ Positional arguments:
       Boundary files
     files_copied
       Files copied for run
+    files_hardlinked
+      Files hardlinked for run
     files_linked
       Files linked for run
     namelist_file

@@ -16,6 +16,8 @@ Positional arguments:
       Boundary files
     files_copied
       Files copied for run
+    files_hardlinked
+      Files hardlinked for run
     files_linked
       Files linked for run
     namelist_file

@@ -14,6 +14,8 @@ Positional arguments:
   TASK
     files_copied
       Files copied for run
+    files_hardlinked
+      Files hardlinked for run
     files_linked
       Files linked for run
     namelist_file

@@ -12,6 +12,10 @@ Optional arguments:
 
 Positional arguments:
   TASK
+    files_copied
+      Files copied for run
+    files_hardlinked
+      Files hardlinked for run
     files_linked
       Files linked for run
     grid_file

@@ -16,6 +16,8 @@ Positional arguments:
       The GRIB control file
     files_copied
       Files copied for run
+    files_hardlinked
+      Files hardlinked for run
     files_linked
       Files linked for run
     namelist_file

@@ -16,6 +16,8 @@ Positional arguments:
       The GRIB control file
     files_copied
       Files copied for run
+    files_hardlinked
+      Files hardlinked for run
     files_linked
       Files linked for run
     namelist_file

@@ -13,7 +13,7 @@
           "minProperties": 1,
           "type": "object"
         },
-        "files_to_link": {
+        "files_to_hardlink": {
           "additionalProperties": {
             "type": "fs_src"
           },

@@ -2,7 +2,7 @@ usage: uw fs hardlink [-h] [--version] [--config-file PATH]
                       [--target-dir PATH] [--cycle CYCLE]
                       [--leadtime LEADTIME] [--dry-run]
                       [--key-path KEY[.KEY...]] [--report] [--quiet]
-                      [--verbose] [--symlink-fallback]
+                      [--verbose] [--fallback {copy,symlink}]
 
 Create hardlinks
 
@@ -29,5 +29,5 @@ Optional arguments:
       Print no logging messages
   --verbose, -v
       Print all logging messages
-  --symlink-fallback
-      Symlink if hardlink fails
+  --fallback {copy,symlink}
+      Alternative if hardlink fails
@@ -35,15 +35,7 @@ field_table:
 
 The path to a :weather-model-io:`valid field-table file<field-table-file>` to be copied into the run directory.
 
-files_to_copy:
-^^^^^^^^^^^^^^
-
-See :ref:`this page <files_yaml>` for details.
-
-files_to_link:
-^^^^^^^^^^^^^^
-
-Identical to ``files_to_copy:`` except that symbolic links will be created in the run directory instead of copies.
+.. include:: /shared/stager.rst
 
 lateral_boundary_conditions:
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^

@@ -25,15 +25,7 @@ configuration_file:
 
 Supports ``base_file:`` and ``update_values:`` blocks (see :ref:`updating_values` for details).
 
-files_to_copy:
-^^^^^^^^^^^^^^
-
-See :ref:`this page <files_yaml>` for details.
-
-files_to_link:
-^^^^^^^^^^^^^^
-
-Identical to ``files_to_copy:`` except that symbolic links will be created in the run directory instead of copies.
+.. include:: /shared/stager.rst
 
 rundir:
 ^^^^^^^

@@ -25,15 +25,7 @@ configuration_file:
 
 Supports ``base_file:`` and ``update_values:`` blocks (see :ref:`updating_values` for details).
 
-files_to_copy:
-^^^^^^^^^^^^^^
-
-See :ref:`this page <files_yaml>` for details.
-
-files_to_link:
-^^^^^^^^^^^^^^
-
-Identical to ``files_to_copy:`` except that symbolic links will be created in the run directory instead of copies.
+.. include:: /shared/stager.rst
 
 rundir:
 ^^^^^^^

@@ -49,12 +49,9 @@ length:
 
 The length of the forecast in integer hours.
 
-files_to_copy:
-^^^^^^^^^^^^^^
+.. include:: /shared/stager.rst
 
-See :ref:`this page <files_yaml>` for details.
-
-To reduce duplication of information in this section, it may be helpful to template the file that depends on the number of cores being used to run the executable. For example, instead of:
+To reduce duplication of information in these sections, it may be helpful to template the file that depends on the number of cores being used to run the executable. For example, instead of:
 
 .. code-block:: text
 
@@ -70,11 +67,6 @@ Jinja2 expressions can be used to reference the number of cores used in executio
      files_to_copy:
        conus.graph.info.part.{{mpas.execution["batchargs"]["cores"]}}: /path/to/conus.graph.info.part.{{mpas.execution["batchargs"]["cores"]}}
 
-files_to_link:
-^^^^^^^^^^^^^^
-
-Identical to ``files_to_copy:`` except that symbolic links will be created in the run directory instead of copies.
-
 namelist:
 ^^^^^^^^^
 

@@ -43,12 +43,9 @@ execution:
 
 See :ref:`this page <execution_yaml>` for details.
 
-files_to_copy:
-^^^^^^^^^^^^^^
+.. include:: /shared/stager.rst
 
-See :ref:`this page <files_yaml>` for details.
-
-To reduce duplication of information in this section, it may be helpful to template the file that depends on the number of cores being used to run the executable. For example, instead of:
+To reduce duplication of information in these sections, it may be helpful to template the file that depends on the number of cores being used to run the executable. For example, instead of:
 
 .. code-block:: text
 
@@ -64,11 +61,6 @@ Jinja2 expressions can be used to reference the number of cores used in executio
      files_to_copy:
        conus.graph.info.part.{{mpas_init.execution["batchargs"]["cores"]}}: /path/to/conus.graph.info.part.{{mpas_init.execution["batchargs"]["cores"]}}
 
-files_to_link:
-^^^^^^^^^^^^^^
-
-Identical to ``files_to_copy:`` except that symbolic links will be created in the run directory instead of copies.
-
 namelist:
 ^^^^^^^^^
 

@@ -21,12 +21,9 @@ execution:
 
 See :ref:`this page <execution_yaml>` for details.
 
-files_to_copy:
-^^^^^^^^^^^^^^
+.. include:: /shared/stager.rst
 
-See :ref:`this page <files_yaml>` for details.
-
-To reduce duplication of information in this section, it may be helpful to reference the config value that specifies the number of cores used to run the executable. For example, instead of:
+To reduce duplication of information in these sections, it may be helpful to reference the config value that specifies the number of cores used to run the executable. For example, instead of:
 
 .. code-block:: text
 
@@ -42,11 +39,6 @@ Jinja2 expressions can be used to reference the number of cores used for executi
      files_to_copy:
        x1.999.graph.info.part.{{ mpassit.execution.batchargs.cores }}: /path/to/x1.999.graph.info.part.{{ mpassit.execution.batchargs.cores }}
 
-files_to_link:
-^^^^^^^^^^^^^^
-
-Identical to ``files_to_copy:`` except that symbolic links will be created in the run directory instead of copies.
-
 namelist:
 ^^^^^^^^^
 

@@ -26,15 +26,7 @@ execution:
 
 See :ref:`here <execution_yaml>` for details.
 
-files_to_copy:
-^^^^^^^^^^^^^^
-
-See :ref:`this page <files_yaml>` for details.
-
-files_to_link:
-^^^^^^^^^^^^^^
-
-Identical to ``files_to_copy:`` except that symbolic links will be created in the run directory instead of copies.
+.. include:: /shared/stager.rst
 
 mask:
 ^^^^^

@@ -21,15 +21,7 @@ execution:
 
 See :ref:`this page <execution_yaml>` for details.
 
-files_to_copy:
-^^^^^^^^^^^^^^
-
-See :ref:`this page <files_yaml>` for details.
-
-files_to_link:
-^^^^^^^^^^^^^^
-
-Identical to ``files_to_copy:`` except that symbolic links will be created in the run directory instead of copies.
+.. include:: /shared/stager.rst
 
 namelist:
 ^^^^^^^^^

@@ -16,15 +16,7 @@ Here is a prototype UW YAML ``upp_assets:`` block, explained in detail below:
 UW YAML for the ``upp_assets:`` Block
 -------------------------------------
 
-files_to_copy:
-^^^^^^^^^^^^^^
-
-See :ref:`this page <files_yaml>` for details.
-
-files_to_link:
-^^^^^^^^^^^^^^
-
-Identical to ``files_to_copy:`` except that symbolic links will be created in the run directory instead of copies.
+.. include:: /shared/stager.rst
 
 namelist:
 ^^^^^^^^^

@@ -0,0 +1,14 @@
+files_to_copy:
+^^^^^^^^^^^^^^
+
+See :ref:`this page <files_yaml>` for details.
+
+files_to_hardlink:
+^^^^^^^^^^^^^^^^^^
+
+Identical to ``files_to_copy:`` except that hard links will be created in the run directory instead of copies, when possible. Otherwise a copy will be created.
+
+files_to_link:
+^^^^^^^^^^^^^^
+
+Identical to ``files_to_copy:`` except that symbolic links will be created in the run directory instead of copies.
@@ -1,4 +1,4 @@
-TARGETS = format lint test-nb unittest
+TARGETS = format lint notebook test-nb unittest
 
 .PHONY: $(TARGETS)
 
@@ -12,6 +12,10 @@ format:
 lint:
 	ruff check tests
 
+notebook:
+	TZ=UTC FAKE_NOW=True jupyter nbconvert --to notebook --inplace --execute *.ipynb
+	jupyter nbconvert --to notebook --coalesce-streams --inplace --ClearMetadataPreprocessor.enabled=True --ClearNotebookMetadataPreprocessor.enabled=True *.ipynb
+
 test: test-nb
 
 test-nb: lint unittest