gpuwm-hex 0.2.3__tar.gz → 0.3.2__tar.gz

{gpuwm_hex-0.2.3 → gpuwm_hex-0.3.2}/MANIFEST.in

@@ -33,40 +33,12 @@ graft verification
 # file the reader does not have" defect the grafts above exist to prevent.
 include evidence/EVIDENCE.md
 
-# ...and one directory of tests that must NOT travel, for the same reason
-# `[tool.setuptools.packages.find] exclude` drops `hexcore.mod` from the
-# wheel.  `graft tests` above is a wildcard, and a wildcard is exactly how the
-# thing nobody listed gets shipped: these tests carry the branch name, the
-# commit and the SHA-256 digests of a private seam that has no remote and
-# exists on one machine.  The package exclusion alone would not stop them --
-# they live under tests/, not under the package.
+# ...and directories and documents that are not part of this distribution:
+# `graft` is a wildcard, so each is held out by name.
 prune tests/mod
 
-# ...and one DOCUMENT that must not travel, caught by the same wildcard logic
-# one directory over.  `graft docs` is a wildcard and
-# `docs/LANE-BRIEFING.md` is not a user document at all: it is this
-# repository's internal working brief, written for whoever picks the tree up
-# next.
-#
-# THE BREAKAGE THIS PREVENTS: an sdist published to PyPI carrying a private
-# LAN address, a home-directory path on the maintainer's own machine, the
-# maintainer's name against the machines he owns, the reservation protocol
-# for those machines, and the existence and card priority of a second,
-# unrelated private effort.  None of that is recallable once uploaded, none
-# of it helps a reader install or run this software, and the file postdates
-# the 0.1.1 sdist -- so this is a leak the previous cut did not have.
-# `tests/test_packaging_declaration.py` builds the real sdist and fails if
-# the briefing reappears in it.
 exclude docs/LANE-BRIEFING.md
 
-# ...and the release checklist, for the same reason and one more.  It is an
-# operating procedure for cutting a release of this distribution, not a
-# document about using it: it names the private assembly tree, the public
-# repository, the maintainer, the scrub policy applied on the way out, and the
-# ordered commands for acts that need the maintainer's explicit approval.
-# Shipping it inside the artefact it describes would publish the recipe for its
-# own publication, and would put governance text into a public tree, which is
-# exactly what the 0.1.0 scrub removed by hand.
 exclude docs/release-checklist-*.md
 
 # Compiled bytecode is a build product of the sources beside it, never an

{gpuwm_hex-0.2.3 → gpuwm_hex-0.3.2}/NOTICE

@@ -11,7 +11,11 @@ MPAS-Atmosphere (LANL / UCAR)
 
 gpuwm-hex reimplements the dynamical core of MPAS-Atmosphere (Model for
 Prediction Across Scales) version 8.4.1 for CUDA devices, with pinned
-source-line citations. MPAS-Atmosphere is developed by the Los Alamos
+source-line citations. The earlier v8.2.3 lane it grew from is still
+carried and selectable, and the standalone Fortran oracles under
+tools/mpas_operator_oracle/ and tools/mpas_step_oracle/ transcribe loop
+bodies of MPAS-Atmosphere v8.2.3 (cited by file and line in each source);
+those transcriptions are MPAS-derived portions under the same terms. MPAS-Atmosphere is developed by the Los Alamos
 National Laboratory and the University Corporation for Atmospheric
 Research / National Center for Atmospheric Research, and is distributed
 under the BSD-3-Clause terms reproduced at the end of this section. Those
@@ -49,7 +53,17 @@ physics_mmm/bl_gwdo.F90, the Kim/YSU orographic gravity-wave-drag and
 flow-blocking scheme from NCAR/MMM. Those files are cited by path and line
 in the module that reimplements them. No source from either upstream is
 copied into this distribution; the citations record what the CUDA operator
-was written against.
+was written against. WRF itself is a public-domain work of NCAR/MMM; this
+distribution states that lineage here rather than relying on the engine's
+NOTICE to carry it.
+
+The longitude arithmetic in src/hexcore/mesh.py
+(_grid_rotate_convert_xl_longitude and reconcile_grid_rotate_longitudes)
+reproduces the convert_xl formula of MPAS-Tools grid_rotate.f90, pinned by
+source digest in that module, so that a rotated mesh's stored longitudes
+can be checked to the producer's own rounding. MPAS-Tools is distributed
+by LANS under the same BSD-3-Clause terms as MPAS-Atmosphere, reproduced
+below; no MPAS-Tools source file is copied into this distribution.
 
 MPAS-Atmosphere license text, retained in full: