What problem does it solve? When a process-based model like FATES moves to a new API version, the parameter set, file format (NetCDF/CDL to JSON), and PFT roster all change, so a site's carefully tuned parameter file cannot simply be copied forward. This Skill performs that migration mechanically and safely, preventing silent errors like calibrated values landing in the wrong PFT slots. ## Core Features & Use Cases - Identity Mapping First: Auto-matches PFT slots by name between old and new parameter files and flags mismatches, so you can override with explicit functional-type mappings before any values move. - Three-Step Port Workflow: Run identity, port, and verify subcommands of tools/port_param_file.py to transfer tuned values onto the new version's template while keeping target-only parameters at defaults. - Post-Port Safety Checks: Catches version-inactivated parameters that must be zeroed after porting to avoid runtime aborts at model initialization. - Use Case: You calibrated a FATES api-31 12-PFT NetCDF file for an arctic site and now need an api-43 14-PFT JSON base file; the Skill remaps repurposed shrub PFTs (e.g. --map 7:10,9:11,10:12), transfers all overlapping tuned values, and verifies the result. ## Quick Start Ask the agent to port your tuned api-31 NetCDF parameter file onto the api-43 JSON template, mapping the arctic shrub PFTs explicitly and verifying the result.
