@neilberkman/sidereon 2.1.0 → 2.1.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,28 @@
1
1
  # Changelog
2
2
 
3
+ ## 2.1.1 - 2026-09-22
4
+
5
+ ### Fixed
6
+
7
+ - Engine update: sidereon 2.1.1 / sidereon-core 2.1.1. CODE predicted
8
+ ionosphere maps resolve to the archive AIUB now serves them from: `cod_prd1`
9
+ is `CODE/IONO/PRD/COD0OPSP0D_<date>0000_01D_01H_GIM.INX.gz` and `cod_prd2`
10
+ is `CODE/IONO/PRD/COD0OPSP1D_<date>0000_01D_01H_GIM.INX.gz`. The
11
+ `CODE/IONO/P1/<year>` and `CODE/IONO/P2/<year>` `COD0OPSPRD` trees they were
12
+ read from stopped receiving issues after 2026-09-21 and are now empty, so
13
+ every predicted-IONEX URL `distributionLocation` and
14
+ `predictedIonexLineCandidates` returned pointed at an object that no longer
15
+ exists. For the dates both layouts carried the objects decompress to the
16
+ same bytes.
17
+ - The two predicted lines now carry distinct official filenames, so
18
+ `productIdentity("cod_prd1", ...)` and `productIdentity("cod_prd2", ...)`
19
+ for one map date differ in `officialFilename` as well as in
20
+ `predictionHorizonDays` and `cacheKey`.
21
+ - `newestPublishedProduct` and `resolveFirstPublishedPredictedIonex` attribute
22
+ only objects under `CODE/IONO/PRD/` to a predicted line, not the rolling
23
+ copies CODE keeps at the tree root.
24
+ - The JavaScript API is unchanged.
25
+
3
26
  ## 2.1.0 - 2026-09-05
4
27
 
5
28
  ### Added
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@neilberkman/sidereon",
3
- "version": "2.1.0",
3
+ "version": "2.1.1",
4
4
  "description": "WebAssembly / JavaScript interface over the sidereon GNSS + astrodynamics engine: SP3 loading and multi-product merge, SPP / RTK (float + fixed) / PPP (float + fixed) positioning, IONEX slant delay, SGP4 and numerical orbit propagation, RINEX observation/navigation/clock parsing, CRINEX (Hatanaka) decoding, observable-domain math (carrier combinations, cycle slips, Hatch smoothing, weighting, velocity, GPS C/A signal), and the astro domain (scale-tagged time, frame transforms, Sun/Moon ephemerides, eclipse / body angles, DOP, passes / visibility, conjunction + collision probability, CDM / OMM / ANTEX parsing, RF link budget)",
5
5
  "type": "module",
6
6
  "license": "MIT",
package/pkg/sidereon.d.ts CHANGED
@@ -11693,13 +11693,15 @@ export function predictBatchSp3(sp3: Sp3, satellites: string[], receivers_ecef_m
11693
11693
  /**
11694
11694
  * Ordered cross-line candidates for one predicted IONEX map date.
11695
11695
  *
11696
- * Both CODE predicted lines publish the same official filename for a map
11697
- * date, but the two-day line is produced a day earlier, so `cod_prd2` is
11698
- * routinely published while `cod_prd1` is still absent when CODE runs
11699
- * behind. Candidates are ordered `cod_prd1` first, all cover the SAME map
11700
- * date (never a neighboring day's map), and each keeps its own line
11701
- * identity so resolved provenance names the line actually served. The walk
11702
- * is opt-in; single-line requests keep their fail-closed behavior.
11696
+ * CODE archives both predicted lines under `CODE/IONO/PRD/`, the one-day
11697
+ * line as `COD0OPSP0D_*` and the two-day line as `COD0OPSP1D_*`, with the
11698
+ * map date in both filenames. The two-day line is produced a day earlier,
11699
+ * so `cod_prd2` is routinely published while `cod_prd1` is still absent
11700
+ * when CODE runs behind. Candidates are ordered `cod_prd1` first, all
11701
+ * cover the SAME map date (never a neighboring day's map), and each keeps
11702
+ * its own line identity so resolved provenance names the line actually
11703
+ * served. The walk is opt-in; single-line requests keep their fail-closed
11704
+ * behavior.
11703
11705
  *
11704
11706
  * Returns an array of `{center, date, sample, issue, filename, url}`.
11705
11707
  */
package/pkg/sidereon.js CHANGED
@@ -28393,13 +28393,15 @@ export function predictBatchSp3(sp3, satellites, receivers_ecef_m, epochs_j2000_
28393
28393
  /**
28394
28394
  * Ordered cross-line candidates for one predicted IONEX map date.
28395
28395
  *
28396
- * Both CODE predicted lines publish the same official filename for a map
28397
- * date, but the two-day line is produced a day earlier, so `cod_prd2` is
28398
- * routinely published while `cod_prd1` is still absent when CODE runs
28399
- * behind. Candidates are ordered `cod_prd1` first, all cover the SAME map
28400
- * date (never a neighboring day's map), and each keeps its own line
28401
- * identity so resolved provenance names the line actually served. The walk
28402
- * is opt-in; single-line requests keep their fail-closed behavior.
28396
+ * CODE archives both predicted lines under `CODE/IONO/PRD/`, the one-day
28397
+ * line as `COD0OPSP0D_*` and the two-day line as `COD0OPSP1D_*`, with the
28398
+ * map date in both filenames. The two-day line is produced a day earlier,
28399
+ * so `cod_prd2` is routinely published while `cod_prd1` is still absent
28400
+ * when CODE runs behind. Candidates are ordered `cod_prd1` first, all
28401
+ * cover the SAME map date (never a neighboring day's map), and each keeps
28402
+ * its own line identity so resolved provenance names the line actually
28403
+ * served. The walk is opt-in; single-line requests keep their fail-closed
28404
+ * behavior.
28403
28405
  *
28404
28406
  * Returns an array of `{center, date, sample, issue, filename, url}`.
28405
28407
  * @param {number} year
Binary file
@@ -11693,13 +11693,15 @@ export function predictBatchSp3(sp3: Sp3, satellites: string[], receivers_ecef_m
11693
11693
  /**
11694
11694
  * Ordered cross-line candidates for one predicted IONEX map date.
11695
11695
  *
11696
- * Both CODE predicted lines publish the same official filename for a map
11697
- * date, but the two-day line is produced a day earlier, so `cod_prd2` is
11698
- * routinely published while `cod_prd1` is still absent when CODE runs
11699
- * behind. Candidates are ordered `cod_prd1` first, all cover the SAME map
11700
- * date (never a neighboring day's map), and each keeps its own line
11701
- * identity so resolved provenance names the line actually served. The walk
11702
- * is opt-in; single-line requests keep their fail-closed behavior.
11696
+ * CODE archives both predicted lines under `CODE/IONO/PRD/`, the one-day
11697
+ * line as `COD0OPSP0D_*` and the two-day line as `COD0OPSP1D_*`, with the
11698
+ * map date in both filenames. The two-day line is produced a day earlier,
11699
+ * so `cod_prd2` is routinely published while `cod_prd1` is still absent
11700
+ * when CODE runs behind. Candidates are ordered `cod_prd1` first, all
11701
+ * cover the SAME map date (never a neighboring day's map), and each keeps
11702
+ * its own line identity so resolved provenance names the line actually
11703
+ * served. The walk is opt-in; single-line requests keep their fail-closed
11704
+ * behavior.
11703
11705
  *
11704
11706
  * Returns an array of `{center, date, sample, issue, filename, url}`.
11705
11707
  */
@@ -28968,13 +28968,15 @@ exports.predictBatchSp3 = predictBatchSp3;
28968
28968
  /**
28969
28969
  * Ordered cross-line candidates for one predicted IONEX map date.
28970
28970
  *
28971
- * Both CODE predicted lines publish the same official filename for a map
28972
- * date, but the two-day line is produced a day earlier, so `cod_prd2` is
28973
- * routinely published while `cod_prd1` is still absent when CODE runs
28974
- * behind. Candidates are ordered `cod_prd1` first, all cover the SAME map
28975
- * date (never a neighboring day's map), and each keeps its own line
28976
- * identity so resolved provenance names the line actually served. The walk
28977
- * is opt-in; single-line requests keep their fail-closed behavior.
28971
+ * CODE archives both predicted lines under `CODE/IONO/PRD/`, the one-day
28972
+ * line as `COD0OPSP0D_*` and the two-day line as `COD0OPSP1D_*`, with the
28973
+ * map date in both filenames. The two-day line is produced a day earlier,
28974
+ * so `cod_prd2` is routinely published while `cod_prd1` is still absent
28975
+ * when CODE runs behind. Candidates are ordered `cod_prd1` first, all
28976
+ * cover the SAME map date (never a neighboring day's map), and each keeps
28977
+ * its own line identity so resolved provenance names the line actually
28978
+ * served. The walk is opt-in; single-line requests keep their fail-closed
28979
+ * behavior.
28978
28980
  *
28979
28981
  * Returns an array of `{center, date, sample, issue, filename, url}`.
28980
28982
  * @param {number} year
Binary file