microlens-submit 0.12.2__tar.gz → 0.16.1__tar.gz

microlens_submit-0.16.1/MANIFEST.in

@@ -0,0 +1,2 @@
+include microlens_submit/assets/rges-pit_logo.png
+include microlens_submit/assets/github-desktop_logo.png

{microlens_submit-0.12.2/microlens_submit.egg-info → microlens_submit-0.16.1}/PKG-INFO

@@ -1,7 +1,9 @@
 Metadata-Version: 2.4
 Name: microlens-submit
-Version: 0.12.2
-Summary: A toolkit for managing microlensing data challenge submissions
+Version: 0.16.1
+Summary: A tool for managing and submitting microlensing solutions
+Home-page: https://github.com/AmberLee2427/microlens-submit
+Author: Amber Malpas
 Author-email: Amber Malpas <malpas.1@osu.edu>, Roman Science Platform Team <roman-science-platform@stsci.edu>
 License: MIT
 Project-URL: Homepage, https://github.com/AmberLee2427/microlens-submit
@@ -27,6 +29,7 @@ Requires-Dist: typer[all]>=0.9.0
 Requires-Dist: rich>=13.0.0
 Requires-Dist: pyyaml>=6.0
 Requires-Dist: markdown>=3.4.0
+Requires-Dist: importlib_resources>=1.0.0; python_version < "3.9"
 Provides-Extra: dev
 Requires-Dist: pytest; extra == "dev"
 Requires-Dist: pytest-cov; extra == "dev"
@@ -37,7 +40,11 @@ Requires-Dist: black; extra == "dev"
 Requires-Dist: isort; extra == "dev"
 Requires-Dist: sphinx; extra == "dev"
 Requires-Dist: sphinx_rtd_theme; extra == "dev"
+Requires-Dist: importlib_resources; extra == "dev"
+Dynamic: author
+Dynamic: home-page
 Dynamic: license-file
+Dynamic: requires-python
 
 <p align="center">
   <a href="https://github.com/AmberLee2427/microlens-submit">
@@ -49,15 +56,13 @@ Dynamic: license-file
 
 *A stateful submission toolkit for the RGES-PIT Microlensing Data Challenge.*
 
-[![PyPI - v0.12.2](https://img.shields.io/pypi/v/microlens-submit.svg)](https://pypi.org/project/microlens-submit/)
-[![CI](https://github.com/AmberLee2427/microlens-submit/actions/workflows/ci.yml/badge.svg)](https://github.com/AmberLee2427/microlens-submit/actions/workflows/ci.yml)
-[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
+[![PyPI - v0.16.0](https://img.shields.io/pypi/v/microlens-submit.svg)](https://pypi.org/project/microlens-submit/)[![Read the Docs](https://readthedocs.org/projects/microlens-submit/badge/?version=latest)](https://microlens-submit.readthedocs.io/en/latest/?badge=latest)[![CI](https://github.com/AmberLee2427/microlens-submit/actions/workflows/ci.yml/badge.svg)](https://github.com/AmberLee2427/microlens-submit/actions/workflows/ci.yml)[![PyPI - Python Version](https://img.shields.io/pypi/pyversions/microlens-submit.svg)](https://pypi.org/project/microlens-submit/)[![License](https://img.shields.io/badge/license-MIT-blue.svg)](https://opensource.org/licenses/MIT)
 
 <br>
 
 `microlens-submit` provides a robust, version-controlled workflow for managing, validating, and packaging your challenge submission over a long period. It supports both a programmatic Python API and a full-featured Command Line Interface (CLI) for language-agnostic use.
 
-Full documentation is hosted on [Read the Docs](https://microlens-submit.readthedocs.io/en/latest/). A comprehensive tutorial notebook is available at `docs/Submission_Tool_Tutorial.ipynb`. Challenge participants who prefer not to use this tool can consult [SUBMISSION_MANUAL.md](SUBMISSION_MANUAL.md) for the manual submission format.
+Full documentation is hosted on [Read the Docs](https://microlens-submit.readthedocs.io/en/latest/). A comprehensive tutorial notebook is available at `docs/Submission_Tool_Tutorial.ipynb`. Challenge participants who prefer not to use this tool can consult the [Submission Manual](https://microlens-submit.readthedocs.io/en/latest/submission_manual.html) for the manual submission format.
 
 ## Key Features
 
@@ -72,10 +77,11 @@ Full documentation is hosted on [Read the Docs](https://microlens-submit.readthe
 * **Environment Capture:** Automatically records your Python dependencies for each specific model fit, ensuring reproducibility.
 * **Optional Posterior Storage:** Record the path to posterior samples for any solution.
 * **Simple Export:** Packages all your active solutions into a clean, standardized `.zip` archive for final submission.
+* **Bulk Import:** Import multiple solutions at once from a CSV file using the `import-solutions` CLI command. Supports column mapping, alias handling, duplicate handling, notes, dry-run, and validation options.
 
 ## Installation
 
-The package is be available on PyPI:
+The package is available on PyPI:
 
 ```bash
 pip install microlens-submit
@@ -87,8 +93,21 @@ The CLI is the recommended way to interact with your submission project.
 
 You can pass ``--no-color`` to any command if your terminal does not support ANSI colors.
 
-1. Initialize your project: `microlens-submit init --team-name "Planet Pounders" --tier "advanced"`
+1. Initialize your project:
+
+   ```bash
+   microlens-submit init --team-name "Planet Pounders" --tier "advanced"
+   # if a project directory was provided to `init`, you should now `cd` into that project
+   ```
+
+   To pass validation, you need to have provided a `repo_url` and `hardware_info` to the project and have a git project initialized in your sumission-project directory.
+
+   ```bash
+   microlens-submit set-repo-url <url> ./
+   microlens-submit set-hardware-info --cpu-details "intel i7 xxx" --ram-gb 32 ./
+   ```
 2. Add a new solution to an event:
+
    ```bash
    microlens-submit add-solution ogle-2025-blg-0042 1S2L \
        --param t0=555.5 \
@@ -96,14 +115,29 @@ You can pass ``--no-color`` to any command if your terminal does not support ANS
        --param tE=25.0 \
        --notes "This is a great fit!"
    ```
+
    Model types must be one of `1S1L`, `1S2L`, `2S1L`, `2S2L`, `1S3L`, `2S3L`, or `other`.
    This will create a new solution and print its unique `solution_id`.
+
    You can run the same command with `--dry-run` first to verify the
    parsed input without saving anything.
-3. Deactivate a solution that didn't work out: `microlens-submit deactivate <solution_id>`
-4. List all solutions for an event: `microlens-submit list-solutions ogle-2025-blg-0042`
-5. Validate solutions and check for issues: `microlens-submit validate-solution <solution_id>`
-6. Export your final submission: `microlens-submit export final_submission.zip`
+
+3. **Bulk import multiple solutions from a CSV file:**
+
+   ```bash
+   microlens-submit import-solutions tests/data/test_import.csv --dry-run
+   ```
+
+   See the file `tests/data/test_import.csv` for a comprehensive example covering all features and edge cases.
+   You can use this file as a template for your own imports.
+
+4. Deactivate a solution that didn't work out: `microlens-submit deactivate <solution_id>`
+
+5. List all solutions for an event: `microlens-submit list-solutions ogle-2025-blg-0042`
+
+6. Validate solutions and check for issues: `microlens-submit validate-solution <solution_id>`
+
+7. Export your final submission: `microlens-submit export final_submission.zip`
 
 **Note:** When you add a solution, it's automatically validated and any warnings are displayed. Use `--dry-run` to check validation without saving.
 
@@ -139,7 +173,8 @@ sub.export("final_submission.zip")
 
 The full development plan can be found in agents.md. Contributions are welcome!
 
-To build and test this project, the development environment needs the following Python libraries. You can provide these to Codex or set up a `requirements-dev.txt` file.
+To build and test this project, install the development dependencies using either `pip install -e .[dev]` or `pip install -r requirements-dev.txt`. These packages are required to run the test suite and are listed in `requirements-dev.txt`.
+After installing the dependencies, run `pre-commit install` to set up the Git hooks for automatic formatting and linting. The development environment needs the following Python libraries.
 
 ### Core Dependencies:
 * **`typer[all]`**: For building the powerful command-line interface. The `[all]` extra ensures shell completion support is included.
@@ -153,9 +188,12 @@ To build and test this project, the development environment needs the following
 * **`build`**: For building the package from the `pyproject.toml` file.
 * **`twine`**: For uploading the final package to PyPI.
 
+### Test Data
+
+A comprehensive test CSV file is provided at `tests/data/test_import.csv`. This file is used in the test suite and can be copied or adapted for your own bulk imports or for development/testing purposes.
+
 ## Citation
 
 If you use **microlens-submit** in your research, please cite the project using
 the metadata provided in the `CITATION.cff` file. Most reference managers can
 import this file directly.
-

{microlens_submit-0.12.2 → microlens_submit-0.16.1}/README.md

@@ -8,15 +8,13 @@
 
 *A stateful submission toolkit for the RGES-PIT Microlensing Data Challenge.*
 
-[![PyPI - v0.12.2](https://img.shields.io/pypi/v/microlens-submit.svg)](https://pypi.org/project/microlens-submit/)
-[![CI](https://github.com/AmberLee2427/microlens-submit/actions/workflows/ci.yml/badge.svg)](https://github.com/AmberLee2427/microlens-submit/actions/workflows/ci.yml)
-[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
+[![PyPI - v0.16.0](https://img.shields.io/pypi/v/microlens-submit.svg)](https://pypi.org/project/microlens-submit/)[![Read the Docs](https://readthedocs.org/projects/microlens-submit/badge/?version=latest)](https://microlens-submit.readthedocs.io/en/latest/?badge=latest)[![CI](https://github.com/AmberLee2427/microlens-submit/actions/workflows/ci.yml/badge.svg)](https://github.com/AmberLee2427/microlens-submit/actions/workflows/ci.yml)[![PyPI - Python Version](https://img.shields.io/pypi/pyversions/microlens-submit.svg)](https://pypi.org/project/microlens-submit/)[![License](https://img.shields.io/badge/license-MIT-blue.svg)](https://opensource.org/licenses/MIT)
 
 <br>
 
 `microlens-submit` provides a robust, version-controlled workflow for managing, validating, and packaging your challenge submission over a long period. It supports both a programmatic Python API and a full-featured Command Line Interface (CLI) for language-agnostic use.
 
-Full documentation is hosted on [Read the Docs](https://microlens-submit.readthedocs.io/en/latest/). A comprehensive tutorial notebook is available at `docs/Submission_Tool_Tutorial.ipynb`. Challenge participants who prefer not to use this tool can consult [SUBMISSION_MANUAL.md](SUBMISSION_MANUAL.md) for the manual submission format.
+Full documentation is hosted on [Read the Docs](https://microlens-submit.readthedocs.io/en/latest/). A comprehensive tutorial notebook is available at `docs/Submission_Tool_Tutorial.ipynb`. Challenge participants who prefer not to use this tool can consult the [Submission Manual](https://microlens-submit.readthedocs.io/en/latest/submission_manual.html) for the manual submission format.
 
 ## Key Features
 
@@ -31,10 +29,11 @@ Full documentation is hosted on [Read the Docs](https://microlens-submit.readthe
 * **Environment Capture:** Automatically records your Python dependencies for each specific model fit, ensuring reproducibility.
 * **Optional Posterior Storage:** Record the path to posterior samples for any solution.
 * **Simple Export:** Packages all your active solutions into a clean, standardized `.zip` archive for final submission.
+* **Bulk Import:** Import multiple solutions at once from a CSV file using the `import-solutions` CLI command. Supports column mapping, alias handling, duplicate handling, notes, dry-run, and validation options.
 
 ## Installation
 
-The package is be available on PyPI:
+The package is available on PyPI:
 
 ```bash
 pip install microlens-submit
@@ -46,8 +45,21 @@ The CLI is the recommended way to interact with your submission project.
 
 You can pass ``--no-color`` to any command if your terminal does not support ANSI colors.
 
-1. Initialize your project: `microlens-submit init --team-name "Planet Pounders" --tier "advanced"`
+1. Initialize your project:
+
+   ```bash
+   microlens-submit init --team-name "Planet Pounders" --tier "advanced"
+   # if a project directory was provided to `init`, you should now `cd` into that project
+   ```
+
+   To pass validation, you need to have provided a `repo_url` and `hardware_info` to the project and have a git project initialized in your sumission-project directory.
+
+   ```bash
+   microlens-submit set-repo-url <url> ./
+   microlens-submit set-hardware-info --cpu-details "intel i7 xxx" --ram-gb 32 ./
+   ```
 2. Add a new solution to an event:
+
    ```bash
    microlens-submit add-solution ogle-2025-blg-0042 1S2L \
        --param t0=555.5 \
@@ -55,14 +67,29 @@ You can pass ``--no-color`` to any command if your terminal does not support ANS
        --param tE=25.0 \
        --notes "This is a great fit!"
    ```
+
    Model types must be one of `1S1L`, `1S2L`, `2S1L`, `2S2L`, `1S3L`, `2S3L`, or `other`.
    This will create a new solution and print its unique `solution_id`.
+
    You can run the same command with `--dry-run` first to verify the
    parsed input without saving anything.
-3. Deactivate a solution that didn't work out: `microlens-submit deactivate <solution_id>`
-4. List all solutions for an event: `microlens-submit list-solutions ogle-2025-blg-0042`
-5. Validate solutions and check for issues: `microlens-submit validate-solution <solution_id>`
-6. Export your final submission: `microlens-submit export final_submission.zip`
+
+3. **Bulk import multiple solutions from a CSV file:**
+
+   ```bash
+   microlens-submit import-solutions tests/data/test_import.csv --dry-run
+   ```
+
+   See the file `tests/data/test_import.csv` for a comprehensive example covering all features and edge cases.
+   You can use this file as a template for your own imports.
+
+4. Deactivate a solution that didn't work out: `microlens-submit deactivate <solution_id>`
+
+5. List all solutions for an event: `microlens-submit list-solutions ogle-2025-blg-0042`
+
+6. Validate solutions and check for issues: `microlens-submit validate-solution <solution_id>`
+
+7. Export your final submission: `microlens-submit export final_submission.zip`
 
 **Note:** When you add a solution, it's automatically validated and any warnings are displayed. Use `--dry-run` to check validation without saving.
 
@@ -98,7 +125,8 @@ sub.export("final_submission.zip")
 
 The full development plan can be found in agents.md. Contributions are welcome!
 
-To build and test this project, the development environment needs the following Python libraries. You can provide these to Codex or set up a `requirements-dev.txt` file.
+To build and test this project, install the development dependencies using either `pip install -e .[dev]` or `pip install -r requirements-dev.txt`. These packages are required to run the test suite and are listed in `requirements-dev.txt`.
+After installing the dependencies, run `pre-commit install` to set up the Git hooks for automatic formatting and linting. The development environment needs the following Python libraries.
 
 ### Core Dependencies:
 * **`typer[all]`**: For building the powerful command-line interface. The `[all]` extra ensures shell completion support is included.
@@ -112,9 +140,12 @@ To build and test this project, the development environment needs the following
 * **`build`**: For building the package from the `pyproject.toml` file.
 * **`twine`**: For uploading the final package to PyPI.
 
+### Test Data
+
+A comprehensive test CSV file is provided at `tests/data/test_import.csv`. This file is used in the test suite and can be copied or adapted for your own bulk imports or for development/testing purposes.
+
 ## Citation
 
 If you use **microlens-submit** in your research, please cite the project using
 the metadata provided in the `CITATION.cff` file. Most reference managers can
 import this file directly.
-

microlens_submit-0.16.1/microlens_submit/__init__.py

@@ -0,0 +1,13 @@
+"""Stateful tools for Microlensing Data Challenge submissions.
+
+``microlens-submit`` manages events and solutions on disk so you can build,
+validate, and export a challenge submission using either the Python API or
+the command line interface.
+"""
+
+__version__ = "0.16.1"
+
+from .models import Event, Solution, Submission
+from .utils import load
+
+__all__ = ["Event", "Solution", "Submission", "load"]

microlens_submit-0.16.1/microlens_submit/cli/__init__.py

@@ -0,0 +1,5 @@
+"""CLI package for microlens-submit."""
+
+from .main import app
+
+__all__ = ["app"]

microlens_submit-0.16.1/microlens_submit/cli/__main__.py

@@ -0,0 +1,6 @@
+"""Entry point for running the CLI as a module."""
+
+from .main import app
+
+if __name__ == "__main__":
+    app()

microlens_submit-0.16.1/microlens_submit/cli/commands/__init__.py

@@ -0,0 +1 @@
+"""CLI commands package for microlens-submit."""

microlens_submit-0.16.1/microlens_submit/cli/commands/dossier.py

@@ -0,0 +1,139 @@
+"""Dossier generation commands for microlens-submit CLI."""
+
+from pathlib import Path
+from typing import Optional
+
+import typer
+from rich.console import Console
+from rich.panel import Panel
+
+from microlens_submit.dossier import generate_dashboard_html, generate_event_page, generate_solution_page
+from microlens_submit.dossier.full_report import generate_full_dossier_report_html
+from microlens_submit.utils import load
+
+console = Console()
+
+
+def generate_dossier(
+    project_path: Path = typer.Argument(Path("."), help="Project directory"),
+    event_id: Optional[str] = typer.Option(
+        None,
+        "--event-id",
+        help="Generate dossier for a specific event only (omit for full dossier)",
+    ),
+    solution_id: Optional[str] = typer.Option(
+        None,
+        "--solution-id",
+        help="Generate dossier for a specific solution only (omit for full dossier)",
+    ),
+    open: bool = typer.Option(
+        False,
+        "--open",
+        help="Open the generated dossier in your web browser after generation.",
+    ),
+) -> None:
+    """Generate an HTML dossier for the submission.
+
+    Use --open to automatically open the main dossier page in your browser after generation.
+    """
+    sub = load(str(project_path))
+    output_dir = Path(project_path) / "dossier"
+
+    if solution_id:
+        # Find the solution across all events (same pattern as other CLI commands)
+        solution = None
+        containing_event_id = None
+        for eid, event in sub.events.items():
+            if solution_id in event.solutions:
+                solution = event.solutions[solution_id]
+                containing_event_id = eid
+                break
+
+        if solution is None:
+            console.print(f"Solution {solution_id} not found", style="bold red")
+            raise typer.Exit(1)
+
+        # Create output directory and assets subdirectory
+        output_dir.mkdir(parents=True, exist_ok=True)
+        (output_dir / "assets").mkdir(exist_ok=True)
+
+        # Generate only the specific solution page
+        event = sub.events[containing_event_id]
+        console.print(
+            Panel(
+                f"Generating dossier for solution {solution_id} in event {containing_event_id}...",
+                style="cyan",
+            )
+        )
+        generate_solution_page(solution, event, sub, output_dir)
+        if open:
+            import webbrowser
+
+            solution_path = output_dir / f"{solution_id}.html"
+            if solution_path.exists():
+                webbrowser.open(solution_path.resolve().as_uri())
+
+    elif event_id:
+        # Generate only the specific event page
+        if event_id not in sub.events:
+            console.print(f"Event {event_id} not found", style="bold red")
+            raise typer.Exit(1)
+
+        # Create output directory and assets subdirectory
+        output_dir.mkdir(parents=True, exist_ok=True)
+        (output_dir / "assets").mkdir(exist_ok=True)
+
+        event = sub.events[event_id]
+        console.print(Panel(f"Generating dossier for event {event_id}...", style="cyan"))
+        generate_event_page(event, sub, output_dir)
+        if open:
+            import webbrowser
+
+            event_path = output_dir / f"{event_id}.html"
+            if event_path.exists():
+                webbrowser.open(event_path.resolve().as_uri())
+
+    else:
+        # Generate full dossier (all events and solutions)
+        console.print(
+            Panel(
+                "Generating comprehensive dossier for all events and solutions...",
+                style="cyan",
+            )
+        )
+        generate_dashboard_html(sub, output_dir)
+
+        # Generate comprehensive printable dossier
+        console.print(Panel("Generating comprehensive printable dossier...", style="cyan"))
+        generate_full_dossier_report_html(sub, output_dir)
+
+        # Replace placeholder in index.html with the real link
+        dashboard_path = output_dir / "index.html"
+        if dashboard_path.exists():
+            with dashboard_path.open("r", encoding="utf-8") as f:
+                dashboard_html = f.read()
+            dashboard_html = dashboard_html.replace(
+                "<!--FULL_DOSSIER_LINK_PLACEHOLDER-->",
+                '<div class="text-center">'
+                '<a href="./full_dossier_report.html" '
+                'class="inline-block bg-rtd-accent text-white py-3 px-6 '
+                "rounded-lg shadow-md hover:bg-rtd-secondary "
+                'transition-colors duration-200 text-lg font-semibold mt-8">'
+                "View Full Comprehensive Dossier (Printable)</a></div>",
+            )
+            with dashboard_path.open("w", encoding="utf-8") as f:
+                f.write(dashboard_html)
+        console.print(Panel("Comprehensive dossier generated!", style="bold green"))
+
+        # Open the main dashboard if requested
+        if open:
+            import webbrowser
+
+            webbrowser.open(dashboard_path.resolve().as_uri())
+
+    console.print(
+        Panel(
+            f"Dossier generated successfully at {output_dir / 'index.html'}",
+            style="bold green",
+        )
+    )

microlens_submit-0.16.1/microlens_submit/cli/commands/export.py

@@ -0,0 +1,177 @@
+"""Export commands for microlens-submit CLI."""
+
+from pathlib import Path
+from typing import Optional
+
+import typer
+from rich.console import Console
+from rich.panel import Panel
+
+from microlens_submit.utils import load
+
+console = Console()
+
+
+def export(
+    output_path: Path,
+    project_path: Path = typer.Argument(Path("."), help="Project directory"),
+) -> None:
+    """Generate a zip archive containing all active solutions.
+
+    This command creates a submission-ready archive. Unlike save operations,
+    export requires all validation checks to pass (complete team info,
+    hardware info, valid parameters, etc.) since this is for actual submission.
+
+    Args:
+        output_path: Path for the output zip file
+        project_path: Directory containing the submission project
+
+    Example:
+        # Export for submission (requires complete submission)
+        microlens-submit export submission.zip ./my_project
+
+    Note:
+        Export is strict and requires complete submissions. Use save operations
+        for saving incomplete work during development.
+    """
+    sub = load(str(project_path))
+    sub.export(str(output_path))
+    console.print(Panel(f"Exported submission to {output_path}", style="bold green"))
+
+
+def remove_event(
+    event_id: str,
+    force: bool = typer.Option(False, "--force", help="Force removal even if event has saved solutions"),
+    project_path: Path = typer.Argument(Path("."), help="Project directory"),
+) -> None:
+    """Remove an entire event and all its solutions from the submission."""
+    submission = load(str(project_path))
+
+    if event_id not in submission.events:
+        typer.echo(f"❌ Event '{event_id}' not found in submission")
+        raise typer.Exit(1)
+
+    event = submission.events[event_id]
+    solution_count = len(event.solutions)
+
+    if not force:
+        typer.echo(f"⚠️  This will permanently remove event '{event_id}' " f"and all {solution_count} solutions.")
+        typer.echo("   This action cannot be undone.")
+        confirm = typer.confirm("Are you sure you want to continue?")
+        if not confirm:
+            typer.echo("❌ Operation cancelled")
+            raise typer.Exit(0)
+
+    try:
+        removed = submission.remove_event(event_id, force=force)
+        if removed:
+            typer.echo(f"✅ Removed event '{event_id}' and all {solution_count} solutions")
+            submission.save()
+        else:
+            typer.echo(f"❌ Failed to remove event '{event_id}'")
+            raise typer.Exit(1)
+    except ValueError as e:
+        typer.echo(f"❌ Cannot remove event: {e}")
+        raise typer.Exit(1)
+
+
+def set_repo_url(
+    repo_url: str = typer.Argument(..., help="GitHub repository URL (e.g. https://github.com/owner/repo)"),
+    project_path: Path = typer.Argument(Path("."), help="Project directory"),
+) -> None:
+    """Set or update the GitHub repository URL in the submission metadata."""
+    sub = load(str(project_path))
+    sub.repo_url = repo_url
+    sub.save()
+    console.print(
+        Panel(
+            f"Set repo_url to {repo_url} in {project_path}/submission.json",
+            style="bold green",
+        )
+    )
+
+
+def set_hardware_info(
+    cpu: Optional[str] = typer.Option(None, "--cpu", help="CPU model/description"),
+    cpu_details: Optional[str] = typer.Option(None, "--cpu-details", help="Detailed CPU information"),
+    memory_gb: Optional[float] = typer.Option(None, "--memory-gb", help="Memory in GB"),
+    ram_gb: Optional[float] = typer.Option(None, "--ram-gb", help="RAM in GB (alternative to --memory-gb)"),
+    platform: Optional[str] = typer.Option(
+        None,
+        "--platform",
+        help="Platform description (e.g., 'Local Analysis', 'Roman Nexus')",
+    ),
+    nexus_image: Optional[str] = typer.Option(None, "--nexus-image", help="Roman Nexus image identifier"),
+    clear: bool = typer.Option(False, "--clear", help="Clear all existing hardware info"),
+    dry_run: bool = typer.Option(False, "--dry-run", help="Show what would be changed without saving"),
+    project_path: Path = typer.Argument(Path("."), help="Project directory"),
+) -> None:
+    """Set or update hardware information in the submission metadata."""
+    sub = load(str(project_path))
+
+    # Initialize hardware_info if it doesn't exist
+    if sub.hardware_info is None:
+        sub.hardware_info = {}
+
+    changes = []
+
+    # Clear existing info if requested
+    if clear:
+        if sub.hardware_info:
+            changes.append("Clear all existing hardware info")
+            sub.hardware_info = {}
+
+    # Set new values
+    if cpu_details is not None:
+        if sub.hardware_info.get("cpu_details") != cpu_details:
+            changes.append(f"Set cpu_details: {cpu_details}")
+            sub.hardware_info["cpu_details"] = cpu_details
+    elif cpu is not None:
+        if sub.hardware_info.get("cpu") != cpu:
+            changes.append(f"Set cpu: {cpu}")
+            sub.hardware_info["cpu"] = cpu
+
+    if memory_gb is not None:
+        if sub.hardware_info.get("memory_gb") != memory_gb:
+            changes.append(f"Set memory_gb: {memory_gb}")
+            sub.hardware_info["memory_gb"] = memory_gb
+    elif ram_gb is not None:
+        if sub.hardware_info.get("ram_gb") != ram_gb:
+            changes.append(f"Set ram_gb: {ram_gb}")
+            sub.hardware_info["ram_gb"] = ram_gb
+
+    if platform is not None:
+        if sub.hardware_info.get("platform") != platform:
+            changes.append(f"Set platform: {platform}")
+            sub.hardware_info["platform"] = platform
+
+    if nexus_image is not None:
+        if sub.hardware_info.get("nexus_image") != nexus_image:
+            changes.append(f"Set nexus_image: {nexus_image}")
+            sub.hardware_info["nexus_image"] = nexus_image
+
+    # Show dry run results
+    if dry_run:
+        if changes:
+            console.print(Panel("Hardware info changes (dry run):", style="cyan"))
+            for change in changes:
+                console.print(f"  • {change}")
+            console.print(f"\nNew hardware_info: {sub.hardware_info}")
+        else:
+            console.print(Panel("No changes would be made", style="yellow"))
+        return
+
+    # Apply changes
+    if changes:
+        sub.save()
+        console.print(
+            Panel(
+                f"Updated hardware info in {project_path}/submission.json",
+                style="bold green",
+            )
+        )
+        for change in changes:
+            console.print(f"  • {change}")
+        console.print(f"\nCurrent hardware_info: {sub.hardware_info}")
+    else:
+        console.print(Panel("No changes made", style="yellow"))