When running independent verification using ReconRes.indpdt_verif(), pseudoproxy generation via job.forward_psms() seems to be constrained to the original prior's time range, which in my case is 850-1850, even when reconstruction files contain data for the full target period (1-2000). This is preventing correct verification of the full instrumental period.
I believe forward_psms() should generate pseudoproxies for the full time range available in the loaded reconstruction files, but it seems to only generates pseudoproxies for 850-1850 (original CCSM4 prior range), missing the 1880-2000 verification period.
I ran the example in the documentation with the main difference being the iCESM prior going from 850-2005 and it worked as intended.
Prior: CCSM4 (850-1850)
Reconstruction period: 1-2000
Verification target: 1880-2000
Proxy Database: PAGES2kv2 (filtered by dt <= 1)
I want to check whether this is an intentional choice in the function or if something is potentially incorrect with the data I am using to run this code.
When running independent verification using ReconRes.indpdt_verif(), pseudoproxy generation via job.forward_psms() seems to be constrained to the original prior's time range, which in my case is 850-1850, even when reconstruction files contain data for the full target period (1-2000). This is preventing correct verification of the full instrumental period.
I believe forward_psms() should generate pseudoproxies for the full time range available in the loaded reconstruction files, but it seems to only generates pseudoproxies for 850-1850 (original CCSM4 prior range), missing the 1880-2000 verification period.
I ran the example in the documentation with the main difference being the iCESM prior going from 850-2005 and it worked as intended.
Prior: CCSM4 (850-1850)
Reconstruction period: 1-2000
Verification target: 1880-2000
Proxy Database: PAGES2kv2 (filtered by dt <= 1)
I want to check whether this is an intentional choice in the function or if something is potentially incorrect with the data I am using to run this code.