@@ -41,8 +41,15 @@ The in-depth contents of this tutorial are organized as follows:
4141**Step-by-Step Guide **
4242######################
4343
44- If your terminal does not support ANSI escape codes, add ``--no-color `` to
45- disable colored output.
44+ In this section, we will go through the complete workflow of using the
45+ ``microlens-submit `` CLI to manage your Roman Microlensing Data Challenge
46+ 2026 submission project. Each step includes detailed explanations, command
47+ examples, and tips for best practices.
48+
49+ .. attention :: Terminal Compatibility
50+
51+ If your terminal does not support ANSI escape codes, add ``--no-color `` to
52+ disable colored output.
4653
4754.. tip :: **Windows PATH tip**
4855
@@ -51,7 +58,7 @@ disable colored output.
5158 microlens-submit `` and run ``py -m microlens_submit.cli --help ``, or add
5259 the Scripts path shown by ``py -m pip show -f microlens-submit `` to PATH.
5360
54- 1. **Initialize your project **
61+ 1. **Initialize Your Project **
5562******************************
5663
5764Start by creating a new submission project with your team information:
@@ -81,8 +88,10 @@ metadata.
8188 - ``--tier ``: Challenge tier ("beginner" or "experienced")
8289 - Project path: Where to create the project directory
8390
84- 2. **Record repository and hardware info **
85- ******************************************
91+ .. _compute_information :
92+
93+ 2. **Record Repository and Hardware Information **
94+ *************************************************
8695
8796Before validation and export, set your repository URL and hardware details.
8897GPU information is optional (Roman Nexus nodes are CPU-only), so omit it if
@@ -126,7 +135,7 @@ can also set solution-level hardware overrides (see
126135`Solution-level hardware overrides <solution_hardware_overrides _>`__
127136for details).
128137
129- 3. **Add your first solution **
138+ 3. **Add Your First Solution **
130139******************************
131140
132141Add a microlensing solution with all required parameters:
@@ -141,6 +150,7 @@ Add a microlensing solution with all required parameters:
141150 --wall-time-hours 3.8 \
142151 --lightcurve-plot-path plots/event123_lc.png \
143152 --lens-plane-plot-path plots/event123_lens.png \
153+ --posterior-path posteriors/chain.h5 \
144154 --notes " Initial fit" \
145155 --higher-order-effect parallax,finite-source
146156
@@ -152,13 +162,14 @@ Add a microlensing solution with all required parameters:
152162
153163.. admonition :: **Optional Metadata**
154164
155- - Log-likelihood and data points for statistical analysis
156- - Compute information for resource tracking
165+ - ` Log-likelihood < solution_comparison _>`__ and data points for statistical analysis
166+ - ` Compute information < compute_information _>`__ for resource tracking
157167 - Physical parameters (``--physical-param Mtot=0.5 ``)
158- - Parameter uncertainties (``--param-uncertainty t0=[1.1,1.3] ``)
168+ - ` Parameter uncertainties < uncertainty_metadata _>`__ (``--param-uncertainty t0=[1.1,1.3] ``)
159169 - Physical parameter uncertainties (``--physical-param-uncertainty Mtot=0.08 ``)
160170 - `Uncertainty metadata <uncertainty_metadata _>`__ (``--uncertainty-method mcmc_posterior --confidence-level 0.68 ``)
161- - Plot paths for visualization files
171+ - `Plot paths <plots _>`__ for visualization files
172+ - `Posterior samples file <posteriors _>`__ (``--posterior-path ``)
162173 - `Notes <notes _>`__ for documentation
163174 - Higher-order effects for advanced models
164175 - `Solution aliases <solution_aliases _>`__ for easier identification
@@ -218,7 +229,7 @@ cluttering the command line.
218229**Parameter File Formats:**
219230---------------------------
220231
221- **Simple format (parameters only ):**
232+ **Simple Format (Parameters Only ):**
222233^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
223234
224235.. code-block:: json
@@ -237,7 +248,7 @@ Or in YAML:
237248 u0: 0.1
238249 tE: 25.0
239250
240- **Structured format (parameters + uncertainties ):**
251+ **Structured Format (Parameters + Uncertainties ):**
241252^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
242253
243254.. code-block:: json
@@ -442,30 +453,30 @@ include rich documentation and visualizations in your submission dossier.
442453=====================
443454
444455After generating a posterior sample (e.g., an MCMC chain), store the file
445- within your project and record its relative path using the Python API: :
456+ within your project and record its relative path using the CLI :
446457
447- >>> sub = microlens_submit.load("/path/to/project")
448- >>> evt = sub.get_event("EVENT123")
449- >>> sol = next(iter(evt.solutions.values()))
450- >>> sol.posterior_path = "posteriors/chain.h5"
451- >>> sol.lightcurve_plot_path = "plots/event123_lc.png"
452- >>> sol.lens_plane_plot_path = "plots/event123_lens.png"
453- >>> sub.save()
458+ .. code-block:: bash
454459
455- .. note::
460+ microlens-submit edit-solution <solution_id> --posterior-path posteriors/chain.h5
461+
462+ .. tip::
456463
457- The CLI does not currently have a command for attaching arbitrary files,
458- but you can use the Python API to set any file paths you want tracked
459- in the solution JSON or edit the JSON files directly. Just make sure to
460- place the files within your project directory and save the relative paths.
464+ Make sure to place the files within your project directory and use the
465+ relative paths.
461466
462467.. _plots:
463468
464469**Plots and visualizations**
465470============================
466471
467- You can attach any plots or visualizations by saving them in your project and
468- tracking their paths in the solution JSON.
472+ The submission packets are limited to two images per solution; the light-curve and lens-plane plots.
473+ You can attach any by saving them in your project and tracking their paths in the solution JSON.
474+
475+ .. code-block:: bash
476+
477+ microlens-submit edit-solution <solution_id> \
478+ --lightcurve-plot-path plots/event123_lc.png \
479+ --lens-plane-plot-path plots/event123_lens.png
469480
470481.. _notes:
471482
@@ -685,6 +696,8 @@ Add alternative models for comparison:
685696 microlens-submit add-solution EVENT123 1S1L \
686697 --param t0=556.0 --param u0=0.2 --param tE=24.5
687698
699+ .. _solution_comparison:
700+
688701**Solution Comparison:**
689702========================
690703
@@ -793,6 +806,9 @@ After creating solutions, you can modify their attributes:
793806 # Add higher-order effects
794807 microlens-submit edit-solution <solution_id> --higher-order-effect parallax,finite-source
795808
809+ # Update plot paths
810+ microlens-submit edit-solution <solution_id> --lightcurve-plot-path plots/new_lc.png
811+
796812 # Clear an attribute
797813 microlens-submit edit-solution <solution_id> --clear-relative-probability
798814
0 commit comments