Remnant-fits.md

@@ -81,7 +81,7 @@ Maximum difference for mf_nonevol: 7.958078640513122e-13
 Maximum difference for e_rad_nonevol: 4.1033842990145786e-13
 ```
 
-We also checked the agreement for the non-precessing approximants. We used the following file: `CIT:/home/charlie.hoy/projects/pesummary_review/remnant_fits/non_precessing/posterior_samples.dat`. We found:
+We also checked the results for the non-precessing case (SEOBNRv4) obtained from Nathan's [independent script](https://ldas-jobs.ligo.caltech.edu/~nathan.johnson-mcdaniel/o3-postprocessing/apply_fits_and_append_samples_for_quick_use_in_O3_pesummary_aligned.py), applied to a copy of [these samples](https://ldas-jobs.ligo.caltech.edu/~charlie.hoy/projects/pesummary_review/remnant_fits/non_precessing/samples/SEOBNRv4_pesummary.dat), with output in `CIT:/home/nathan.johnson-mcdaniel/GW190412/pesummary_check/SEOBNRv4_pesummary_check.dat`. The check is carried out with [this script](https://ldas-jobs.ligo.caltech.edu/~nathan.johnson-mcdaniel/o3-postprocessing/check_pesummary_results.py) and gives
 
 ```bash
 max af difference:  2.22044604925e-16
@@ -97,7 +97,7 @@ moved to [subpage](Remnant-fits-review-comments)
 ## sign-off
 
 * Nathan & David sign off on the version from !242 on 09 March 2020. ✔
-* As a caveat, we have only seen the one output page for a precessing run above. The special cases of spin-aligned or non-spinning cases (not relevant for immediate urgent applications) are to be double-checked later. 🚧
+* As a caveat, we have only seen the single output page each for aligned-spin and precessing runs, linked above. The special case of a non-spinning run (not relevant for immediate urgent applications) is to be double-checked later. Additionally, in the future, the aligned-spin remnant sample names will be changed to not use the `_non_evolved` suffix, for consistency with the cbcBayesPostProc naming convention. 🚧
 
 
 # Spin evolution for nrutils fits