Subj : Re: MakeNL v3.4.1 Release
To   : Andrew Leary
From : Ward Dossche
Date : Fri Jul 27 2018 01:25:02

Andrew,
 
AL> Discussions are underway on dealing with Marc's other issue with MakeNL;
AL> he feels that there should not be an age limit on segments.  The original
AL> Ben Baker version of MakeNL would only go back 2 weeks before the
AL> upcoming week; the current MakeNL_NG release goes back 6 weeks before the
AL> upcoming week.
 
I have segments that go back years and they don't cause a problem. REGION21 
(Norway) dor example dates from August 22nd 2011 and its full name is 
REGION21.238. Region-38 (Yugoslavia etc dates from Jan.4 2011 and is named 
REGION38.077, so there even isn't any serious correlation between the 
file-production date and the Julian date.
 
These are the statements I use in the "files"-section:
 
Region 20     region20.*    2:20/0
Region 21     region21.*    2:21/0
Region 22     region22.*    2:22/0
Region 23     region23.*    2:23/0
Region 24     region24.*    2:24/0
Region 25     region25.*    2:25/0
Region 28     region28.*    2:28/0
Region 31     region31.*    2:31/0
Region 33     region33.*    2:33/0
Region 34     region34.*    2:34/0
region 38     region38.*    2:38/0
region 40     region40.*    2:40/0
region 42     region42.*    2:42/0
region 45     region45.*    2:45/0
region 46     region46.*    2:46/0
region 48     region48.*    2:48/0
region 49     region49.*    2:49/0
region 50     region50.*    2:50/0
region 56     region56.*    2:56/0
Zone    1     zone1.*
Zone    3     zone3.*
Zone    4     zone4.*
 
Not the age of a segment nor its Julian date are of any importance ...
 
Shouldn't that be enough for RC19?
 
 \%/@rd

--- D'Bridge 3.98
 * Origin: Many Glacier / Protect - Preserve - Conserve (2:292/854)

.