microlens-submit 0.16.2__tar.gz → 0.16.4__tar.gz

microlens_submit-0.16.4/CHANGELOG.md

@@ -0,0 +1,282 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [0.16.4] - 2026-01-14
+
+### Added
+- Added `remove-event`/`remove-solution` CLI commands and `remove_event`/`remove_solution` API helpers with a `--force` guard for hard deletes.
+- Added `git_dir` metadata plus `set-git-dir` to capture Git info when the repo lives outside the submission directory.
+- Added optional GPU fields in `hardware_info` (`gpu.model`, `gpu.count`, `gpu.memory_gb`) alongside platform/OS capture.
+- Added non-Nexus hardware auto-fill using `psutil` for CPU and memory details.
+- Added conda-forge recipe (`conda/recipe/meta.yaml`) to the version bump script (`scripts/bump_version`).
+- Added sha256 update in `conda/recipe/meta.yaml` to the release workflow.
+- Added a workflow release job to copy the local updated version on the conda-forge recipe to the feedstock fork (`AmberLee2427/microlens-submit-feedstock`) and send a PR, after PyPI release.
+
+
+### Changed
+- Updated tiers to `beginner`/`experienced`; event ID validation now uses inclusive ranges and 3-digit IDs for `2018-test`.
+- CLI numeric parsing now accepts leading decimals like `.001`.
+- Clarified quickstart/tutorial guidance around working directories and hardware info requirements.
+
+
+### Fixed
+- CSV import now skips blank rows to avoid NoneType parsing errors.
+- Validation messaging now highlights missing bands when flux parameters are provided.
+- Improved Windows notes editor fallback for better default editor selection.
+
+
+## [0.16.3] - 2025-10-28
+
+### Added
+-  Publish to `conda-forge`.
+
+### Fixed
+- Include `pyproject.toml` and other metadata in the sdist so `pip install .` works (fixes conda builds).
+
+## [0.16.2] - 2025-10-28
+
+### Added
+- conda build to release action
+- local `.env` support
+- Zenodo doi automation
+- build wheel and conda build install smoke tests on Mac, Linux, and Windows, python 3.8 and 3.11
+
+
+## [0.16.1] - 2025-10-27
+
+### Added
+- Release automation
+- CI now installs from the wheel across 3.8/3.12 to mirror beta testers’ reports
+
+### Changed
+- `README.md` to clarify Quickstart
+
+### Fixed
+- `importlib_resources` version bug
+
+
+## [0.16.0] - 2024-12-19
+
+### Added
+- **Tier Validation System**: Comprehensive tier-based validation for challenge submissions
+  - New `tier_validation.py` module with support for "standard", "advanced", "test", "2018-test", and "None" tiers
+  - Event ID validation against tier-specific event lists
+  - CLI tier validation with fallback to "None" for invalid tiers
+  - Comprehensive tier validation tests in `tests/test_tier_validation.py`
+- **Enhanced Validation Logic**: Improved parameter validation and solution completeness checking
+  - Enhanced `validate_parameters.py` with better error messages and validation rules
+  - Improved validation for higher-order effects and parameter consistency
+  - Better handling of parameter uncertainties and type validation
+  - Enhanced solution completeness checking with more detailed feedback
+- **Dossier Generation Enhancements**: Improved HTML dossier generation and browser integration
+  - Added model_type display at the top of each solution section in full dossier reports
+  - Added `--open` flag to `microlens-submit generate-dossier` CLI command for automatic browser opening
+  - Added `open: bool = False` parameter to `generate_dashboard_html()` API function
+  - Enhanced dossier navigation and metadata display
+- **Submission Manual Integration**: Converted SUBMISSION_MANUAL.md to reStructuredText format and integrated into Sphinx documentation
+  - Moved submission manual to `docs/submission_manual.rst` for better documentation integration
+  - Updated all internal links and references to point to the new documentation location
+  - Added GitHub link to validate_submission.py script in the submission manual
+  - Removed old markdown file and logo references for cleaner documentation structure
+
+### Changed
+- **Validation System Architecture**: Improved validation workflow and error handling
+  - Enhanced CLI validation commands with better error reporting
+  - Improved validation integration across all CLI commands
+  - Better handling of validation warnings vs errors
+  - Enhanced parameter validation with more detailed feedback
+- **Code Quality & Pre-commit Integration**: Comprehensive code cleanup and formatting improvements
+  - Fixed all pre-commit hook violations including line length, unused imports, and style issues
+  - Resolved f-string formatting issues in CLI commands
+  - Fixed line length violations in dossier generation code
+  - Removed unused imports across the codebase
+  - Ensured all tests pass in both Python 3.8 and 3.11 environments
+- **Documentation Structure**: Improved documentation organization and accessibility
+  - Integrated submission manual into main documentation site
+  - Updated internal documentation links and references
+  - Enhanced documentation consistency and maintainability
+  - Updated API documentation and tutorial examples
+
+### Fixed
+- **Code Quality**: Resolved all pre-commit hook violations
+  - Fixed f-string formatting issues in CLI commands
+  - Resolved line length violations in dossier generation code
+  - Removed unused imports across the codebase
+  - Improved code consistency and maintainability
+- **Validation Logic**: Enhanced parameter validation and error handling
+  - Improved validation for higher-order effects
+  - Better handling of parameter uncertainties
+  - Enhanced solution completeness checking
+  - More detailed validation feedback and error messages
+
+## [0.15.0] - 2024-12-19
+
+### Added
+- New tier validation system with support for "standard", "advanced", "test", "2018-test", and "None" tiers
+- Event ID validation against tier-specific event lists
+- CLI tier validation with fallback to "None" for invalid tiers
+- Comprehensive tier validation tests
+
+### Changed
+- Renamed "basic" tier to "standard" for better naming
+- Updated tier hierarchy: standard < advanced (removed "expert" tier)
+- Simplified to two challenge tiers: "standard" and "advanced"
+
+## [0.14.0] - 2024-12-19
+
+### Added
+- **Modular Architecture**: Complete refactoring of the codebase for improved maintainability
+  - Split monolithic `dossier.py` into modular `dossier/` package with specialized modules
+  - Refactored CLI into `cli/` package with commands organized into separate modules
+  - Created `dossier/generator.py` for HTML generation logic
+  - Created `dossier/templates.py` for template management
+  - Created `dossier/utils.py` for dossier-specific utilities
+  - Created `cli/commands/` directory with specialized command modules
+  - Created `cli/utils.py` for CLI-specific utilities
+- **Enhanced Error Messaging**: Comprehensive error handling improvements
+  - Added actionable suggestions for common typos and parameter errors
+  - Integrated validation warnings with helpful guidance
+  - Enhanced CLI error messages with specific recommendations
+  - Added parameter validation with user-friendly error descriptions
+- **Improved CLI Help**: Enhanced command-line interface usability
+  - Added [BASIC] and [ADVANCED] tags to help users understand option complexity
+  - Improved option descriptions with practical usage examples
+  - Enhanced help text for complex parameters like `--limb-darkening-model`
+  - Added usage examples in command docstrings for better user guidance
+
+### Changed
+- **Code Organization**: Improved project structure and maintainability
+  - Separated concerns between dossier generation, CLI commands, and utilities
+  - Enhanced code readability and debugging capabilities
+  - Maintained backward compatibility with existing API and CLI interfaces
+  - Preserved all existing functionality while improving internal organization
+- **Documentation**: Updated internal documentation to reflect new modular structure
+  - Enhanced docstrings with usage examples and parameter descriptions
+  - Improved code comments for better developer experience
+  - Maintained user-facing documentation consistency
+
+### Fixed
+- **Maintainability**: Resolved technical debt through modularization
+  - Eliminated monolithic files that were difficult to maintain
+  - Improved test organization and coverage
+  - Enhanced code reusability and separation of concerns
+- **User Experience**: Better error handling and guidance
+  - More helpful error messages with actionable suggestions
+  - Clearer CLI help text with practical examples
+  - Improved parameter validation with user-friendly feedback
+
+## [0.13.0] - 2024-12-19
+
+### Added
+- **Bulk CSV Import**: New CLI command `import-solutions` and API function `import_solutions_from_csv()` for importing multiple solutions from a CSV file in one step
+  - Supports column mapping via YAML parameter map files
+  - Handles solution aliases with uniqueness validation within events
+  - Supports duplicate handling (error/override/ignore), notes, dry-run, and validation options
+  - Properly converts literal `\n` characters to actual newlines in notes from CSV files
+  - See the tutorial and README for usage examples
+- **Solution Aliases**: Human-readable identifiers for solutions with automatic uniqueness validation
+  - Aliases are displayed prominently in dossier generation and CLI output
+  - Integrated into all CLI commands that reference solutions
+  - Supports alias-based solution identification and management
+- **Enhanced Notes Handling**: Improved handling of notes with literal escape sequences
+  - CSV import automatically converts literal `\n` and `\r` to actual newlines
+  - Added `convert_escapes` parameter to `set_notes()` method for controlled conversion
+  - Maintains backward compatibility with existing notes functionality
+- **Test Data**: Added `tests/data/test_import.csv` as a comprehensive test file for CSV import functionality
+  - Used in both CLI and API tests as a real-world example and template for users
+  - Includes various parameter types, aliases, notes, and edge cases for testing
+
+### Changed
+- **Code Quality**: Improved formatting and readability throughout the codebase
+  - Added proper spacing and logical grouping in dense functions
+  - Enhanced code maintainability and debugging capabilities
+- **Documentation**: Updated tutorial, README, and API documentation to cover CSV import and alias features
+- **CLI Enhancements**: Added alias support to all solution-related CLI commands
+
+### Fixed
+- **Notes Rendering**: Fixed issue where literal `\n` characters in notes were rendered as text instead of line breaks in HTML
+  - CSV import now properly converts escape sequences to actual newlines
+  - Maintains compatibility with existing notes that don't need conversion
+
+## [0.12.2] - 2024-12-19
+
+### Fixed
+- **Critical Bug Fix**: Renamed `Solution.validate()` method to `Solution.run_validation()` to resolve Pydantic conflict
+  - Pydantic was interpreting the `validate` method as a field validator, causing import errors
+  - This was breaking Sphinx documentation generation and module imports
+  - All references updated across API, CLI, tests, and documentation
+  - Method functionality remains identical, only the name changed
+
+### Changed
+- Updated all documentation and examples to use `run_validation()` instead of `validate()`
+- Updated CLI commands and help text for consistency
+- Updated test suite to use the new method name
+
+## [0.12.1] - 2024-12-19
+
+### Added
+- **New CLI Command**: `set-hardware-info` for managing compute platform information
+  - Supports setting CPU, memory, platform, and Nexus image details
+  - Includes `--clear`, `--dry-run`, and update options
+  - Integrates with dossier generation for hardware documentation
+- **Enhanced Documentation**: Comprehensive improvements to Sphinx documentation
+  - Expanded API reference with detailed examples and best practices
+  - Enhanced tutorial with step-by-step workflow and troubleshooting
+  - Improved index page with key features and quick start guide
+  - Added custom CSS styling for RGES-PIT color scheme
+- **Example Parameter Files**: Created comprehensive example parameter files
+  - `tests/example_params.yaml` and `tests/example_params.json`
+  - Demonstrates different parameter formats, uncertainties, and model types
+  - Useful for testing and tutorial purposes
+
+### Changed
+- **Version Update**: Bumped version from v0.12.0-dev to v0.12.1
+- **Documentation**: Updated all version references across codebase
+- **Tutorial**: Updated CLI commands in `Submission_Tool_Tutorial.ipynb` to match current syntax
+- **GitHub Logo**: Ensured GitHub logo is properly packaged and included in dossier generation
+
+### Fixed
+- **CI Test Failures**: Fixed test assertions for CLI comparison and validation commands
+  - Updated table header counting logic for solution comparison output
+  - Added missing repo_url setting in validation tests
+- **Documentation Build**: Improved Sphinx configuration for better autodoc and theme options
+
+## [0.12.0] - 2024-12-18
+
+### Added
+- **Comprehensive Documentation**: Complete Sphinx documentation with API reference, tutorial, and examples
+- **Enhanced Dossier Generation**: Improved HTML dashboard with better styling and navigation
+- **Parameter File Support**: Added support for JSON and YAML parameter files in CLI
+- **Validation System**: Centralized parameter validation with comprehensive error checking
+- **Hardware Information**: Automatic detection and manual setting of compute platform details
+- **Notes Management**: Enhanced markdown notes support with file-based editing
+- **Solution Comparison**: BIC-based solution ranking and relative probability calculation
+- **Export Improvements**: Better handling of external files and automatic path updates
+
+### Changed
+- **API Improvements**: Enhanced Solution and Submission classes with better validation
+- **CLI Enhancements**: More robust command-line interface with better error handling
+- **Project Structure**: Improved organization with better separation of concerns
+
+### Fixed
+- **Bug Fixes**: Various fixes for data persistence, validation, and export functionality
+- **Documentation**: Comprehensive docstring updates with Google style formatting
+
+## [0.11.0] - 2024-12-17
+
+### Added
+- **Initial Release**: Basic submission management functionality
+- **Core API**: Solution, Event, and Submission classes
+- **CLI Interface**: Basic command-line tools for project management
+- **Export Functionality**: ZIP archive creation for submissions
+
+### Changed
+- **Project Structure**: Organized code into logical modules
+- **Documentation**: Basic README and docstrings
+
+### Fixed
+- **Initial Implementation**: Core functionality for microlensing submission management

microlens_submit-0.16.4/CITATION.cff

@@ -0,0 +1,9 @@
+cff-version: 1.2.0
+message: "If you use microlens-submit, please cite it as below."
+title: "microlens-submit"
+version: "0.16.4"
+authors:
+  - family-names: Malpas
+    given-names: Amber
+url: "https://github.com/AmberLee2427/microlens-submit"
+doi: "10.5281/zenodo.18246117"

{microlens_submit-0.16.2 → microlens_submit-0.16.4}/MANIFEST.in

@@ -1,2 +1,6 @@
 include microlens_submit/assets/rges-pit_logo.png
 include microlens_submit/assets/github-desktop_logo.png
+include pyproject.toml
+include README.md
+include CHANGELOG.md
+include CITATION.cff

{microlens_submit-0.16.2/microlens_submit.egg-info → microlens_submit-0.16.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: microlens-submit
-Version: 0.16.2
+Version: 0.16.4
 Summary: A tool for managing and submitting microlensing solutions
 Home-page: https://github.com/AmberLee2427/microlens-submit
 Author: Amber Malpas
@@ -29,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: psutil>=5.9.0
 Requires-Dist: importlib_resources>=1.0.0; python_version < "3.9"
 Provides-Extra: dev
 Requires-Dist: pytest; extra == "dev"
@@ -97,15 +98,19 @@ You can pass ``--no-color`` to any command if your terminal does not support ANS
 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
+   microlens-submit init --team-name "Planet Pounders" --tier "experienced" ./my_submission
+   cd ./my_submission
    ```
 
-   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.
+   If you prefer to initialize inside an existing folder, run `microlens-submit init` without a path after `cd` into it.
+
+   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. On Roman Nexus, you can use `microlens-submit nexus-init` to auto-populate hardware info.
 
    ```bash
    microlens-submit set-repo-url <url> ./
    microlens-submit set-hardware-info --cpu-details "intel i7 xxx" --ram-gb 32 ./
+   # if your git repo lives elsewhere:
+   microlens-submit set-git-dir /path/to/repo ./
    ```
 2. Add a new solution to an event:
 
@@ -152,7 +157,7 @@ import microlens_submit
 # Load or create the project
 sub = microlens_submit.load(project_path="./my_challenge_submission")
 sub.team_name = "Planet Pounders"
-sub.tier = "advanced"
+sub.tier = "experienced"
 
 # Get an event and add a solution
 evt = sub.get_event("ogle-2025-blg-0042")
@@ -201,15 +206,15 @@ import this file directly.
 
 Bibtex:
 ```
-@software{malpas_2025_17460500,
+@software{malpas_2025_18246117,
   author       = {Malpas, Amber},
   title        = {microlens-submit},
   month        = oct,
   year         = 2025,
   publisher    = {Zenodo},
-  version      = {v0.16.1},
-  doi          = {10.5281/zenodo.17460500},
-  url          = {https://doi.org/10.5281/zenodo.17460500},
+  version      = {v0.16.3},
+  doi          = {10.5281/zenodo.18246117},
+  url          = {https://doi.org/10.5281/zenodo.18246117},
 }
 ```
 
@@ -217,4 +222,4 @@ Cite without version:
 Malpas, A. (2025). microlens-submit. Zenodo. https://doi.org/10.5281/zenodo.17459752
 
 Cite current version:
-Malpas, A. (2025). microlens-submit (v0.16.1). Zenodo. https://doi.org/10.5281/zenodo.17459753
+Malpas, A. (2025). microlens-submit (v0.16.3). Zenodo. https://doi.org/10.5281/zenodo.17468488

{microlens_submit-0.16.2 → microlens_submit-0.16.4}/README.md

@@ -48,15 +48,19 @@ You can pass ``--no-color`` to any command if your terminal does not support ANS
 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
+   microlens-submit init --team-name "Planet Pounders" --tier "experienced" ./my_submission
+   cd ./my_submission
    ```
 
-   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.
+   If you prefer to initialize inside an existing folder, run `microlens-submit init` without a path after `cd` into it.
+
+   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. On Roman Nexus, you can use `microlens-submit nexus-init` to auto-populate hardware info.
 
    ```bash
    microlens-submit set-repo-url <url> ./
    microlens-submit set-hardware-info --cpu-details "intel i7 xxx" --ram-gb 32 ./
+   # if your git repo lives elsewhere:
+   microlens-submit set-git-dir /path/to/repo ./
    ```
 2. Add a new solution to an event:
 
@@ -103,7 +107,7 @@ import microlens_submit
 # Load or create the project
 sub = microlens_submit.load(project_path="./my_challenge_submission")
 sub.team_name = "Planet Pounders"
-sub.tier = "advanced"
+sub.tier = "experienced"
 
 # Get an event and add a solution
 evt = sub.get_event("ogle-2025-blg-0042")
@@ -152,15 +156,15 @@ import this file directly.
 
 Bibtex:
 ```
-@software{malpas_2025_17460500,
+@software{malpas_2025_18246117,
   author       = {Malpas, Amber},
   title        = {microlens-submit},
   month        = oct,
   year         = 2025,
   publisher    = {Zenodo},
-  version      = {v0.16.1},
-  doi          = {10.5281/zenodo.17460500},
-  url          = {https://doi.org/10.5281/zenodo.17460500},
+  version      = {v0.16.3},
+  doi          = {10.5281/zenodo.18246117},
+  url          = {https://doi.org/10.5281/zenodo.18246117},
 }
 ```
 
@@ -168,4 +172,4 @@ Cite without version:
 Malpas, A. (2025). microlens-submit. Zenodo. https://doi.org/10.5281/zenodo.17459752
 
 Cite current version:
-Malpas, A. (2025). microlens-submit (v0.16.1). Zenodo. https://doi.org/10.5281/zenodo.17459753
+Malpas, A. (2025). microlens-submit (v0.16.3). Zenodo. https://doi.org/10.5281/zenodo.17468488

{microlens_submit-0.16.2 → microlens_submit-0.16.4}/microlens_submit/__init__.py

@@ -5,7 +5,7 @@ validate, and export a challenge submission using either the Python API or
 the command line interface.
 """
 
-__version__ = "0.16.2"
+__version__ = "0.16.4"
 
 from .models import Event, Solution, Submission
 from .utils import load

{microlens_submit-0.16.2 → microlens_submit-0.16.4}/microlens_submit/cli/commands/export.py

@@ -42,10 +42,13 @@ def export(
 
 def remove_event(
     event_id: str,
-    force: bool = typer.Option(False, "--force", help="Force removal even if event has saved solutions"),
+    force: bool = typer.Option(False, "--force", help="Required to remove an event (prevents accidents)"),
     project_path: Path = typer.Argument(Path("."), help="Project directory"),
 ) -> None:
-    """Remove an entire event and all its solutions from the submission."""
+    """Remove an entire event and all its solutions from the submission.
+
+    This action is destructive and requires --force to proceed.
+    """
     submission = load(str(project_path))
 
     if event_id not in submission.events:
@@ -57,13 +60,11 @@ def remove_event(
 
     if not force:
         typer.echo(
-            f"{symbol('warning')}  This will permanently remove event '{event_id}' and all {solution_count} solutions."
+            f"{symbol('warning')}  Refusing to remove event '{event_id}' without --force "
+            f"({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(f"{symbol('error')} Operation cancelled")
-            raise typer.Exit(0)
+        typer.echo(f"{symbol('hint')} Consider deactivating solutions instead, or re-run with --force to proceed.")
+        raise typer.Exit(0)
 
     try:
         removed = submission.remove_event(event_id, force=force)
@@ -94,11 +95,33 @@ def set_repo_url(
     )
 
 
+def set_git_dir(
+    git_dir: Path = typer.Argument(..., help="Path to the git working tree"),
+    project_path: Path = typer.Argument(Path("."), help="Project directory"),
+) -> None:
+    """Set or update the git working tree path in the submission metadata."""
+    sub = load(str(project_path))
+    git_dir_path = git_dir.expanduser().resolve()
+    if not git_dir_path.exists():
+        raise typer.BadParameter(f"git_dir does not exist: {git_dir_path}")
+    sub.git_dir = str(git_dir_path)
+    sub.save()
+    console.print(
+        Panel(
+            f"Set git_dir to {git_dir_path} 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)"),
+    gpu: Optional[str] = typer.Option(None, "--gpu", help="GPU model/description"),
+    gpu_count: Optional[int] = typer.Option(None, "--gpu-count", help="Number of GPUs"),
+    gpu_memory_gb: Optional[float] = typer.Option(None, "--gpu-memory-gb", help="GPU memory per device in GB"),
     platform: Optional[str] = typer.Option(
         None,
         "--platform",
@@ -153,6 +176,24 @@ def set_hardware_info(
             changes.append(f"Set nexus_image: {nexus_image}")
             sub.hardware_info["nexus_image"] = nexus_image
 
+    if any(value is not None for value in (gpu, gpu_count, gpu_memory_gb)):
+        gpu_info = sub.hardware_info.get("gpu")
+        if not isinstance(gpu_info, dict):
+            gpu_info = {}
+        if gpu is not None:
+            if gpu_info.get("model") != gpu:
+                changes.append(f"Set gpu.model: {gpu}")
+                gpu_info["model"] = gpu
+        if gpu_count is not None:
+            if gpu_info.get("count") != gpu_count:
+                changes.append(f"Set gpu.count: {gpu_count}")
+                gpu_info["count"] = gpu_count
+        if gpu_memory_gb is not None:
+            if gpu_info.get("memory_gb") != gpu_memory_gb:
+                changes.append(f"Set gpu.memory_gb: {gpu_memory_gb}")
+                gpu_info["memory_gb"] = gpu_memory_gb
+        sub.hardware_info["gpu"] = gpu_info
+
     # Show dry run results
     if dry_run:
         if changes:

{microlens_submit-0.16.2 → microlens_submit-0.16.4}/microlens_submit/cli/commands/init.py

@@ -17,6 +17,7 @@ def init(
     team_name: str = typer.Option(..., help="Team name"),
     tier: str = typer.Option(..., help="Challenge tier"),
     project_path: Path = typer.Argument(Path("."), help="Project directory"),
+    show_warnings: bool = True,
 ) -> None:
     """Create a new submission project in the specified directory.
 
@@ -29,7 +30,7 @@ def init(
 
     Args:
         team_name: Name of the participating team (e.g., "Team Alpha").
-        tier: Challenge tier level (e.g., "basic", "advanced").
+        tier: Challenge tier level (e.g., "beginner", "experienced").
         project_path: Directory where the project will be created.
             Defaults to current directory if not specified.
 
@@ -38,10 +39,10 @@ def init(
 
     Example:
         # Create project in current directory
-        microlens-submit init --team-name "Team Alpha" --tier "advanced"
+        microlens-submit init --team-name "Team Alpha" --tier "experienced"
 
         # Create project in specific directory
-        microlens-submit init --team-name "Team Beta" --tier "basic" ./my_submission
+        microlens-submit init --team-name "Team Beta" --tier "beginner" ./my_submission
 
         # Project structure created:
         # ./my_submission/
@@ -100,12 +101,15 @@ def init(
         )
 
     # Run warnings-only validation
-    warnings = sub.run_validation_warnings()
-    if warnings:
-        console.print(f"[yellow]{symbol('warning')}  Project initialized with warnings:[/yellow]")
-        for warning in warnings:
-            console.print(f"   [yellow]• {warning}[/yellow]")
-        console.print(f"[yellow]{symbol('hint')} These warnings will become errors when saving or exporting.[/yellow]")
+    if show_warnings:
+        warnings = sub.run_validation_warnings()
+        if warnings:
+            console.print(f"[yellow]{symbol('warning')}  Project initialized with warnings:[/yellow]")
+            for warning in warnings:
+                console.print(f"   [yellow]• {warning}[/yellow]")
+            console.print(
+                f"[yellow]{symbol('hint')} These warnings will become errors when saving or exporting.[/yellow]"
+            )
 
     # Try to save, but don't fail if there are validation errors
     try:
@@ -134,13 +138,13 @@ def nexus_init(
 
     Args:
         team_name: Name of the participating team (e.g., "Team Alpha").
-        tier: Challenge tier level (e.g., "basic", "advanced").
+        tier: Challenge tier level (e.g., "beginner", "experienced").
         project_path: Directory where the project will be created.
             Defaults to current directory if not specified.
 
     Example:
         # Initialize project with Nexus platform info
-        microlens-submit nexus-init --team-name "Team Alpha" --tier "advanced" ./project
+        microlens-submit nexus-init --team-name "Team Alpha" --tier "experienced" ./project
 
         # This will automatically detect:
         # - CPU model from /proc/cpuinfo
@@ -152,7 +156,7 @@ def nexus_init(
         environment. It will silently skip any environment information that
         cannot be detected (e.g., if running outside of Nexus).
     """
-    init(team_name=team_name, tier=tier, project_path=project_path)
+    init(team_name=team_name, tier=tier, project_path=project_path, show_warnings=False)
     sub = load(str(project_path))
     sub.autofill_nexus_info()