satnogs-predict 1.0__tar.gz → 1.2__tar.gz

{satnogs_predict-1.0 → satnogs_predict-1.2}/CHANGELOG.md

@@ -1,5 +1,21 @@
 # Changelog
 
+## 1.2
+
+### Added
+
+- `generate_fake_tle()` encodes catalog numbers 100000–339999 in Alpha-5 format.
+
+### Fixed
+
+- `generate_fake_tle()` raises `ValueError` for catalog numbers outside 0–339999. Previously 6-digit numbers were silently truncated to their first five digits.
+
+## 1.1
+
+### Fixed
+
+- `generate_fake_tle()` writes the epoch year as the last two digits of the year. Previously it used the first two digits (e.g. `20` for 2026), so every generated TLE had an epoch in 2020.
+
 ## 1.0
 
 ### Breaking Changes

{satnogs_predict-1.0 → satnogs_predict-1.2}/CONTRIBUTING.md

@@ -11,6 +11,7 @@
   * [Respond to review comments](#respond-to-review-comments)
   * [Don’t get discouraged - or impatient](#dont-get-discouraged-or-impatient)
   * [Sign your work - the Developer’s Certificate of Origin](#sign-your-work-the-developers-certificate-of-origin)
+  * [Generative AI / LLM Policy](#generative-ai--llm-policy)
   * [References](#references)
 
 ## Introduction ##
@@ -22,7 +23,7 @@ It is based on Linux kernel patch submission guidelines.
 
 All Libre Space Foundation projects code is maintained under Git.
 Obtain a copy of the source code using `git clone`.
-Development usually takes place under `master` or `dev` branch.
+Development usually takes place under `main`, `master` or `dev` branch.
 
 ## Separate the changes ##
 
@@ -39,16 +40,16 @@ The point to remember is that each commit should make an easily understood chang
 Each commit should be justifiable on its own merits.
 
 When creating a merge request from a series of commits, take special care to ensure that the software builds and runs properly after each commit in the series.
-Developers using `git bisect` to track down a problem can end up splitting your merge request at any point; they will not thank you if you introduce bugs in the middle.
+Developers using `git bisect` to track down a problem can end up splitting your merge request at any point; not thanking you if you introduce bugs in the middle.
 
 If you cannot condense your merge request into a smaller set of commits, then only submit say 15 or so at a time and wait for review and integration.
 
-Never commit binary files.
+Never commit binary files or statically generated code.
 Once they are part of Git repository history they cannot be removed.
 
 ## Quality check of the changes ##
 
-Continuous Integration will check your changes automatically once you create a merge request.
+Continuous Integration checks your changes automatically once you create a merge request.
 Nevertheless, local quality check should also be done before submitting a merge request.
 The checks can include:
   * Static code analysis and coverage
@@ -78,10 +79,10 @@ See [Separate the changes](#separate-the-changes).
 
 Create commit or merge requests descriptions that are self-contained.
 This benefits both the maintainers and reviewers.
-Always use your real name and e-mail address for committing changes.
+Always use a known identity and email address for committing changes.
 
 If the commit fixes a reported issue, refer to that bug entry by issue number.
-The issue will be closed automatically after merge, if it matches [this regular expression](https://docs.gitlab.com/ce/user/project/issues/automatic_issue_closing.html).
+The issue closes automatically after merge, if it matches [this regular expression](https://docs.gitlab.com/ce/user/project/issues/automatic_issue_closing.html).
 
 ## Create a merge request ##
 
@@ -91,7 +92,7 @@ Merge requests must not contain other merge requests; re-base your commits if ne
 
 ## Respond to review comments ##
 
-Your merge request will almost certainly get comments from reviewers on ways in which it can be improved.
+Your merge request almost certainly gets comments from reviewers on ways in which it can be improved.
 You must respond to those comments; ignoring reviewers is a good way to get ignored in return.
 Be sure to tell the reviewers what changes you are making and to thank them for their time.
 Code review is a tiring and time-consuming process, and reviewers sometimes get grumpy.
@@ -106,9 +107,9 @@ Wait for a minimum of one week before pinging reviewers - possibly longer during
 
 ## Sign your work - the Developer’s Certificate of Origin ##
 
-To improve tracking of who did what, especially with commits that can percolate to their final resting place in Libre Space Foundation projects code-base through several layers of maintainers, we’ve introduced a “sign-off” procedure on commits.
+To improve tracking of who did what, especially with commits that can percolate to their final resting place in Libre Space Foundation projects code-base through several layers of maintainers, a “sign-off” procedure on commits is enforced.
 
-The sign-off is a simple line at the end of the explanation for the commit, which certifies that you wrote it or otherwise have the right to pass it on as an open-source patch.
+The sign-off is a simple line at the end of the explanation for the commit, which certifies that you wrote it or otherwise have the right to pass it on as an open source patch.
 The rules are pretty simple:
 
 if you can certify the below:
@@ -138,7 +139,7 @@ then you just add a line saying:
 
 `Signed-off-by: Random J Developer <random@developer.example.org>`
 
-using your real name (sorry, no pseudonyms or anonymous contributions.)
+using a known identity (sorry, no anonymous contributions.)
 
 If you are a maintainer, sometimes you need to slightly modify commits order to merge them.
 If you stick strictly to rule (c), you should ask the submitter to rediff, but this is a totally counter-productive waste of time and energy.
@@ -152,6 +153,83 @@ Signed-off-by: Random J Developer <random@developer.example.org>
 Signed-off-by: Lucky K Maintainer <lucky@maintainer.example.org>
 ```
 
+## Generative AI / LLM Policy ##
+
+We appreciate that we can't realistically police how you author your merge requests, which includes whether you employ large-language model (LLM)-based development tools.
+So, we don't.
+
+However, due to both legal and human reasons, we have to establish boundaries.
+
+### Overview ###
+
+- We take the responsibility for this project very seriously and we expect you to take your responsibility for your contributions seriously, too.
+  This used to be a given, but it changed now that a merge request is just one prompt away.
+- Every contribution has to be backed by a human who unequivocally owns the copyright for all changes.
+  No LLM bots in `Co-authored-by:`s.
+- Repeated slop contributions are unacceptable, and will be closed without review.
+  We reserve the right to exclude contributors who continue to submit such material.
+- Absolutely no unsupervised agentic tools like OpenClaw.
+
+By submitting a merge request, you certify that:
+
+- You are the author of the contribution or have the legal right to submit it.
+- You either hold the copyright to the changes or have explicit legal authorization to contribute them under this project's license.
+- You understand the code.
+- You accept full responsibility for it.
+
+### Legal ###
+
+There is ongoing legal uncertainty regarding the copyright status of LLM-generated works and their provenance.
+Because of this, allowing contributions by LLMs has unpredictable consequences for the copyright status of this project - even when leaving aside possible copyright violations due to plagiarism.
+
+### Human ###
+
+As the makers of software that is used by many people worldwide and with a reputation for high-quality maintenance, we take our responsibility to our users very seriously.
+No matter what LLM vendors or boosters on LinkedIn tell you, we have to manually review every change before merging, because it's our responsibility to keep the project stable.
+
+Please understand that by opening low-quality merge requests you're not helping anyone.
+Worse, you're [poisoning the open source ecosystem](https://lwn.net/Articles/1058266/) that was precarious even before the arrival of LLM tools.
+Having to wade through plausible-looking-but-low-quality merge requests and trying to determine which ones are legit is extremely demoralizing and has already burned out many good maintainers.
+
+In particular, note that [code reviews are a social process](https://blog.glyph.im/2026/03/what-is-code-review-for.html) and are *not* intended to catch bugs in PRs created by an LLM.
+If you submit a merge request, we expect you to engage with reviewers and learn from the review, not
+simply update the prompt that generated the PR and regenerate the code.
+
+Put bluntly, we have no time or interest to become part of your vibe coding loop where you drop LLM slop at our door, we spend time and energy to review it, and you just feed it back into the LLM for another iteration.
+
+This dynamic is especially pernicious because it poisons the well for mentoring new contributors which we are committed to.
+
+### Summary ###
+
+In practice, this means:
+
+- Merge requests that have an LLM product listed as co-author can't be merged and will be closed without further discussion.
+  We cannot risk the copyright status of this project.
+
+  If you used LLM tools during development, you may still submit - but you must remove any LLM co-author tags and take full ownership of every line.
+
+- By submitting a merge request, you take full technical and legal responsibility for the contents of the merge request and promise that you hold the copyright for the changes submitted.
+
+  "An LLM wrote it" is *not* an acceptable response to questions or critique.
+  If you cannot explain and defend the changes you submit, do not submit them and open a high-quality bug report or feature request instead.
+
+- Accounts that exercise bot-like behavior, like automated mass merge requests, will be permanently banned, whether they belong to a human or not.
+
+- LLM-generated comments must be concise and accurate, and you must be prepared to stand by them.
+  Do not post summaries unless you are certain that they add value to the discussion.
+  Remember that all LLM output *looks* plausible.
+  When using these tools, it's your responsibility to ensure that the output is correct, and useful.
+
+- Remember that LLM generated content is generally easier for you to produce, but *harder* for others to read, review or interpret.
+  Prioritising your time over that of others is contrary to the project's code of conduct.
+  Verbose, repetitive, or off topic comments may be marked as spam.
+
+### Thanks ###
+
+This LLM policy was based on the policy of the `pip` and `attrs` project.
+Many thanks to them for developing it.
+
 ## References ##
 
   * Linux kernel documentation - [Submitting patches: the essential guide to getting your code into the kernel](https://www.kernel.org/doc/html/latest/process/submitting-patches.html)
+  * pip AI policy - [Generative AI / LLM Policy](https://github.com/pypa/pip/blob/main/AI_POLICY.md)

{satnogs_predict-1.0 → satnogs_predict-1.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: satnogs-predict
-Version: 1.0
+Version: 1.2
 Summary: A package for calculating passes and observation windows for satellites.
 Requires-Python: >=3.11
 Description-Content-Type: text/markdown

{satnogs_predict-1.0 → satnogs_predict-1.2}/src/satnogs_predict/tle.py

@@ -29,6 +29,19 @@ class FakeTLEParameters:
 
 DEFAULT_FAKE_TLE_PARAMETERS = FakeTLEParameters()
 
+# Alpha-5 prefix letters for 10..33; I and O are skipped to avoid confusion with 1 and 0.
+_ALPHA5_LETTERS = "ABCDEFGHJKLMNPQRSTUVWXYZ"
+_MAX_ALPHA5_CATALOG_NUM = 339_999
+
+
+def _format_catalog_number(catalog_num: int) -> str:
+    if 0 <= catalog_num <= 99_999:
+        return f"{catalog_num:05d}"
+    if 100_000 <= catalog_num <= _MAX_ALPHA5_CATALOG_NUM:
+        prefix, remainder = divmod(catalog_num, 10_000)
+        return f"{_ALPHA5_LETTERS[prefix - 10]}{remainder:04d}"
+    raise ValueError(f"catalog_num must be between 0 and {_MAX_ALPHA5_CATALOG_NUM}")
+
 
 def _tle_checksum(line_without_checksum: str) -> int:
     total = 0
@@ -71,17 +84,18 @@ def generate_fake_tle(
     right_ascension = (observer_location.lst_hours_at(skyfield_time) * 15.0) % 360.0
     mean_anomaly = latitude % 360.0
 
-    epoch_year = epoch.year
+    catalog_number = _format_catalog_number(params.catalog_num)
+    epoch_year = epoch.year % 100
     epoch_day = _epoch_day_of_year_fraction(epoch)
 
     line0 = params.name.ljust(24)
 
     line1_no_checksum = (
-        "1 {:5.5}{:.1} {:8.8} {:.2}{:012.8f} {:>10.10} {:>8.8} {:>8.8} 0 {:>4.4}".format(
-            f"{params.catalog_num:05d}",
+        "1 {:5.5}{:.1} {:8.8} {:02d}{:012.8f} {:>10.10} {:>8.8} {:>8.8} 0 {:>4.4}".format(
+            catalog_number,
             params.classifier,
             params.cospar_id,
-            str(epoch_year),
+            epoch_year,
             epoch_day,
             params.mean_motion_first,
             params.mean_motion_second,
@@ -92,7 +106,7 @@ def generate_fake_tle(
 
     line2_no_checksum = (
         "2 {:>5.5} {:>8.8} {:>8.4f} {:>7.7} {:>8.8} {:>8.4f} {:>11.11}{:>5.5}".format(
-            f"{params.catalog_num:05d}",
+            catalog_number,
             params.inclination,
             right_ascension,
             params.eccentricity,

{satnogs_predict-1.0 → satnogs_predict-1.2}/src/satnogs_predict.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: satnogs-predict
-Version: 1.0
+Version: 1.2
 Summary: A package for calculating passes and observation windows for satellites.
 Requires-Python: >=3.11
 Description-Content-Type: text/markdown

{satnogs_predict-1.0 → satnogs_predict-1.2}/src/satnogs_predict.egg-info/scm_file_list.json

@@ -3,50 +3,50 @@
     ".gitignore",
     ".gitlab-ci.yml",
     ".pre-commit-config.yaml",
-    "CHANGELOG.md",
     ".python-version",
-    "README.md",
+    "CHANGELOG.md",
     "CONTRIBUTING.md",
-    "uv.lock",
-    "pyproject.toml",
     "LICENSE",
+    "README.md",
+    "docs/docs.md",
+    "pyproject.toml",
     "setup.py",
-    "tests/conftest.py",
-    "tests/__init__.py",
-    "tests/helpers.py",
-    "tests/test_tle.py",
-    "tests/integration/test_fake_tle_integration.py",
-    "tests/domain/test_time.py",
-    "tests/domain/test_planner_domain.py",
-    "tests/domain/test_required_fields.py",
-    "tests/domain/test_orbit.py",
-    "tests/domain/test_observer.py",
-    "tests/domain/test_window.py",
-    "tests/planning/test_planner.py",
-    "tests/propagation/test_propagator.py",
-    "tests/core/test_engine.py",
-    "tests/constraints/test_constraints.py",
     "src/satnogs_predict/__init__.py",
-    "src/satnogs_predict/py.typed",
-    "src/satnogs_predict/utils.py",
-    "src/satnogs_predict/tle.py",
+    "src/satnogs_predict/constraints/__init__.py",
+    "src/satnogs_predict/constraints/constraints.py",
+    "src/satnogs_predict/core/__init__.py",
+    "src/satnogs_predict/core/engine.py",
+    "src/satnogs_predict/domain/__init__.py",
     "src/satnogs_predict/domain/constraints.py",
-    "src/satnogs_predict/domain/time.py",
+    "src/satnogs_predict/domain/geometry.py",
     "src/satnogs_predict/domain/observer.py",
-    "src/satnogs_predict/domain/validation.py",
+    "src/satnogs_predict/domain/orbit.py",
     "src/satnogs_predict/domain/planner.py",
-    "src/satnogs_predict/domain/__init__.py",
+    "src/satnogs_predict/domain/time.py",
+    "src/satnogs_predict/domain/validation.py",
     "src/satnogs_predict/domain/window.py",
-    "src/satnogs_predict/domain/geometry.py",
-    "src/satnogs_predict/domain/orbit.py",
-    "src/satnogs_predict/planning/planner.py",
     "src/satnogs_predict/planning/__init__.py",
+    "src/satnogs_predict/planning/planner.py",
     "src/satnogs_predict/propagation/__init__.py",
     "src/satnogs_predict/propagation/propagator.py",
-    "src/satnogs_predict/core/engine.py",
-    "src/satnogs_predict/core/__init__.py",
-    "src/satnogs_predict/constraints/constraints.py",
-    "src/satnogs_predict/constraints/__init__.py",
-    "docs/docs.md"
+    "src/satnogs_predict/py.typed",
+    "src/satnogs_predict/tle.py",
+    "src/satnogs_predict/utils.py",
+    "tests/__init__.py",
+    "tests/conftest.py",
+    "tests/constraints/test_constraints.py",
+    "tests/core/test_engine.py",
+    "tests/domain/test_observer.py",
+    "tests/domain/test_orbit.py",
+    "tests/domain/test_planner_domain.py",
+    "tests/domain/test_required_fields.py",
+    "tests/domain/test_time.py",
+    "tests/domain/test_window.py",
+    "tests/helpers.py",
+    "tests/integration/test_fake_tle_integration.py",
+    "tests/planning/test_planner.py",
+    "tests/propagation/test_propagator.py",
+    "tests/test_tle.py",
+    "uv.lock"
   ]
 }

satnogs_predict-1.2/src/satnogs_predict.egg-info/scm_version.json

@@ -0,0 +1,8 @@
+{
+  "tag": "1.2",
+  "distance": 0,
+  "node": "g536f81b75ea7f5aed4ff17646823a9e6a9aa2c9a",
+  "dirty": false,
+  "branch": "HEAD",
+  "node_date": "2026-10-23"
+}

{satnogs_predict-1.0 → satnogs_predict-1.2}/tests/integration/test_fake_tle_integration.py

@@ -82,12 +82,15 @@ class TestFakeTleIntegration:
             TLE_EPOCH + timedelta(hours=3),
         )
         passes = find_passes(satellite, observer, time_range)
+        # Use a pass away from zenith with a gradual azimuth sweep.
         thepass = next(
             thepass
             for thepass in passes
-            if thepass.start_sample.azimuth_deg < 220.0 and thepass.end_sample.azimuth_deg > 330.0
+            if thepass.max_altitude_sample.altitude_deg < 80.0
+            and thepass.start_sample.azimuth_deg < 260.0
+            and thepass.end_sample.azimuth_deg > 300.0
         )
-        constraint = AzimuthWindowConstraint(az_start=220.0, az_end=330.0)
+        constraint = AzimuthWindowConstraint(az_start=260.0, az_end=300.0)
         context = ConstraintContext(satellite=satellite, observer=observer)
 
         constrained = constraint.apply(thepass, context=context)
@@ -95,5 +98,5 @@ class TestFakeTleIntegration:
         assert constrained.constraint_applied_result == ConstraintAppliedResult.MODIFIED
         assert constrained.start_sample.instant > thepass.start_sample.instant
         assert constrained.end_sample.instant < thepass.end_sample.instant
-        assert 220.0 <= constrained.start_sample.azimuth_deg <= 330.0
-        assert 220.0 <= constrained.end_sample.azimuth_deg <= 330.0
+        assert 260.0 <= constrained.start_sample.azimuth_deg <= 300.0
+        assert 260.0 <= constrained.end_sample.azimuth_deg <= 300.0

satnogs_predict-1.2/tests/test_tle.py

@@ -0,0 +1,114 @@
+from __future__ import annotations
+
+from datetime import datetime, timezone
+
+import pytest
+from skyfield.api import EarthSatellite, load  # type: ignore[import-untyped]
+
+from satnogs_predict import generate_fake_tle
+from satnogs_predict.tle import FakeTLEParameters
+
+ts = load.timescale()
+
+
+def _checksum(line_without_checksum: str) -> int:
+    total = 0
+    for char in line_without_checksum:
+        if char.isdigit():
+            total += int(char)
+        elif char == "-":
+            total += 1
+    return total % 10
+
+
+class TestGenerateFakeTle:
+    @pytest.mark.parametrize(
+        ("date_iso", "expected_epoch"),
+        [
+            ("2026-10-01T12:00:00+00:00", "26274.50000000"),
+            ("2006-01-01T00:00:00+00:00", "06001.00000000"),
+            ("1999-12-31T12:00:00+00:00", "99365.50000000"),
+            ("2024-02-29T06:00:00+00:00", "24060.25000000"),
+            ("2026-01-01T01:00:00+02:00", "25365.95833333"),
+        ],
+    )
+    def test_given_aware_date_when_generated_then_preserves_epoch(
+        self, date_iso: str, expected_epoch: str
+    ) -> None:
+        date = datetime.fromisoformat(date_iso)
+        tle = generate_fake_tle(latitude=37.9838, longitude=23.7275, date=date)
+
+        assert tle.line1[18:32] == expected_epoch
+        sat = EarthSatellite(tle.line1, tle.line2, tle.line0, ts)
+        assert abs((sat.epoch.utc_datetime() - date).total_seconds()) < 0.001
+
+    def test_given_valid_input_when_generated_then_returns_parseable_tle(self) -> None:
+        tle = generate_fake_tle(
+            latitude=37.9838,
+            longitude=23.7275,
+            date=datetime(2026, 3, 6, 12, 0, 0, tzinfo=timezone.utc),
+        )
+
+        assert len(tle.line1) == 69
+        assert len(tle.line2) == 69
+        assert tle.line1[-1] == str(_checksum(tle.line1[:-1]))
+        assert tle.line2[-1] == str(_checksum(tle.line2[:-1]))
+
+        sat = EarthSatellite(tle.line1, tle.line2, tle.line0, ts)
+        assert sat.name == tle.line0.strip()
+
+    def test_given_same_input_when_generated_twice_then_result_is_deterministic(self) -> None:
+        date = datetime(2026, 3, 6, 12, 0, 0, tzinfo=timezone.utc)
+
+        tle1 = generate_fake_tle(latitude=10.0, longitude=20.0, date=date)
+        tle2 = generate_fake_tle(latitude=10.0, longitude=20.0, date=date)
+
+        assert tle1 == tle2
+
+    def test_given_naive_date_when_generated_then_raises(self) -> None:
+        with pytest.raises(ValueError, match="timezone-aware"):
+            generate_fake_tle(
+                latitude=0.0,
+                longitude=0.0,
+                date=datetime(2026, 3, 6, 12, 0, 0),
+            )
+
+    @pytest.mark.parametrize(
+        ("catalog_num", "expected_field"),
+        [
+            (0, "00000"),
+            (25544, "25544"),
+            (99999, "99999"),
+            (100000, "A0000"),
+            (148493, "E8493"),
+            (182345, "J2345"),
+            (234567, "P4567"),
+            (339999, "Z9999"),
+        ],
+    )
+    def test_given_catalog_num_when_generated_then_encodes_alpha5(
+        self, catalog_num: int, expected_field: str
+    ) -> None:
+        tle = generate_fake_tle(
+            latitude=0.0,
+            longitude=0.0,
+            date=datetime(2026, 3, 6, 12, 0, 0, tzinfo=timezone.utc),
+            params=FakeTLEParameters(catalog_num=catalog_num),
+        )
+
+        assert tle.line1[2:7] == expected_field
+        assert tle.line2[2:7] == expected_field
+        sat = EarthSatellite(tle.line1, tle.line2, tle.line0, ts)
+        assert sat.model.satnum == catalog_num
+
+    @pytest.mark.parametrize("catalog_num", [-1, 340000, 1000000])
+    def test_given_out_of_range_catalog_num_when_generated_then_raises(
+        self, catalog_num: int
+    ) -> None:
+        with pytest.raises(ValueError, match="catalog_num"):
+            generate_fake_tle(
+                latitude=0.0,
+                longitude=0.0,
+                date=datetime(2026, 3, 6, 12, 0, 0, tzinfo=timezone.utc),
+                params=FakeTLEParameters(catalog_num=catalog_num),
+            )

satnogs_predict-1.0/src/satnogs_predict.egg-info/scm_version.json

@@ -1,8 +0,0 @@
-{
-  "tag": "1.0",
-  "distance": 0,
-  "node": "g302d7309b6fa2c41ed4296c82e03362c8a8350b7",
-  "dirty": false,
-  "branch": "HEAD",
-  "node_date": "2026-07-01"
-}

satnogs_predict-1.0/tests/test_tle.py

@@ -1,53 +0,0 @@
-from __future__ import annotations
-
-from datetime import datetime, timezone
-
-import pytest
-from skyfield.api import EarthSatellite, load  # type: ignore[import-untyped]
-
-from satnogs_predict import generate_fake_tle
-
-ts = load.timescale()
-
-
-def _checksum(line_without_checksum: str) -> int:
-    total = 0
-    for char in line_without_checksum:
-        if char.isdigit():
-            total += int(char)
-        elif char == "-":
-            total += 1
-    return total % 10
-
-
-class TestGenerateFakeTle:
-    def test_given_valid_input_when_generated_then_returns_parseable_tle(self) -> None:
-        tle = generate_fake_tle(
-            latitude=37.9838,
-            longitude=23.7275,
-            date=datetime(2026, 3, 6, 12, 0, 0, tzinfo=timezone.utc),
-        )
-
-        assert len(tle.line1) == 69
-        assert len(tle.line2) == 69
-        assert tle.line1[-1] == str(_checksum(tle.line1[:-1]))
-        assert tle.line2[-1] == str(_checksum(tle.line2[:-1]))
-
-        sat = EarthSatellite(tle.line1, tle.line2, tle.line0, ts)
-        assert sat.name == tle.line0.strip()
-
-    def test_given_same_input_when_generated_twice_then_result_is_deterministic(self) -> None:
-        date = datetime(2026, 3, 6, 12, 0, 0, tzinfo=timezone.utc)
-
-        tle1 = generate_fake_tle(latitude=10.0, longitude=20.0, date=date)
-        tle2 = generate_fake_tle(latitude=10.0, longitude=20.0, date=date)
-
-        assert tle1 == tle2
-
-    def test_given_naive_date_when_generated_then_raises(self) -> None:
-        with pytest.raises(ValueError, match="timezone-aware"):
-            generate_fake_tle(
-                latitude=0.0,
-                longitude=0.0,
-                date=datetime(2026, 3, 6, 12, 0, 0),
-            )