Overview Version History Q & A Rating & Review
NC Filtered Git Diff
Compare NC files against their Git HEAD version, with all noise patterns defined in your NCComparisonConfig.json hierarchy filtered out before the diff is shown.
Features
Right-click any .nc file in the Explorer → Compare with Git HEAD (filtered)
Automatically loads and merges the 3-level NCComparisonConfig.json hierarchy:
Global — {Git-Root}/_SOFTWARE/DATA/NCComparisonConfig.json
PTA-level — {PTA-Folder}/NCComparisonConfig/NCComparisonConfig.json
PP-specific — {PTA-Folder}/NCComparisonConfig/{PP-Name}/NCComparisonConfig.json
Opens the VS Code built-in side-by-side diff editor with cleaned text
Graceful degradation: if a config level is missing, it is silently skipped
Folder Structure Expected
{Git-Root}/
├── _SOFTWARE/DATA/NCComparisonConfig.json ← Level 1 (global)
└── {PTA-Folder}/ ← identified by "Baseline Output" subfolder
├── Baseline Output/
│ └── {PP-Name}/ ← post-processor name
│ └── *.nc ← files to compare
└── NCComparisonConfig/
├── NCComparisonConfig.json ← Level 2 (PTA)
└── {PP-Name}/
└── NCComparisonConfig.json ← Level 3 (PP-specific)
{
"Ignores": [
{
"Find": "; -- DATE:\\s+[0-9]{1,2}[\\/\\.][0-9]{1,2}[\\/\\.][0-9]{4}.*",
"Replace": "; -- DATE: XX/XX/XXXX XX:XX:XX",
"Comment": "Date with Time"
}
]
}
Find — ECMAScript regular expression (global + multiline flags applied automatically)
Replace — Replacement string (supports $1, $2 capture group references)
Comment — Optional human-readable description
Requirements
VS Code ≥ 1.85
Built-in Git extension must be enabled
The .nc file must be tracked in the Git repository