The 'shadow' process is the way that LRPG keeps the Operational LRP and the 
New Cycle LRP separate, but both updated without conflicts arising between them.
The Shadow is run to sequester New-Cycle plan windows from the standard LRP release 
process, yet keeps them updated as the PCs and PIs continue to modify the proposals.  

The shadow runs as a component of the lrp-batch
process, generating an updated 'New Cycle' LRP which is then assimilated into the
*next* night's batch LRP.  If any 'new cycle' proposals have been installed in the
operational LRP, they will 'trump' any windows in the Shadow or 'NT' LRP.  Prior to
execution of the Shadow, the operational LRP is merged into a copy of the shadow
(with any NT windows overwritten by the operational LRP windows).   And then an
lrp-batch-like LRP is done to generate a new NT LRP.







 Activation of the Shadow.

Here are some notes about activation/deactivation of the shadow process.


uvm res ops-lrpg
edit ops-lrpg
	(see block below)
uvm rep ops-lrpg


There are a large number of parameters associated with the SHADOW which
need to be updated prior to activation:


"""
#
# Old C19 values:
##setenv LRP_SHADOW_CRITERIA	build_c19_criteria_t01
#setenv LRP_SHADOW_START1	11.274
#setenv LRP_SHADOW_START2	11.214
#setenv LRP_SHADOW_END1		12.275
#setenv LRP_SHADOW_END2		13.091
#setenv LRP_SHADOW_LRESADJ	c19_b02_t01_adj_lt
#setenv LRP_SHADOW_VRESADJ	c19_b02_t01_adj_val
#
# Old C20 values:
#setenv LRP_SHADOW_CRITERIA	build_c20_criteria_b04t07	# 12-08-06 ij update to one used in build
#setenv LRP_SHADOW_CRITICS	auto-critic
#setenv LRP_SHADOW_START1	12.275
#setenv LRP_SHADOW_START2	12.235
#setenv LRP_SHADOW_END1		13.329		# end of cycle + 8 weeks
#setenv LRP_SHADOW_END2		14.125
#setenv LRP_SHADOW_LRESADJ       c20_build01_t05_adj_lt
#setenv LRP_SHADOW_VRESADJ	reslimit_ultimate_flat_plus_tail_adj_val
#
# New C21 values:
setenv LRP_SHADOW_CRITERIA	build_c21_saaflex_and_np_on_GAon		# 13-07-24 ij update to one used in build.
setenv LRP_SHADOW_CRITICS	auto-critic					# critics off for B18T02, but on for SHADOW maintenance.
setenv LRP_SHADOW_START1	13.273						# start trying to schedule new C21 entrants at this date.
setenv LRP_SHADOW_START2	13.238						# fallback date if not schedulable after START1
setenv LRP_SHADOW_END1		15.030						# end of nominal cycle tail
setenv LRP_SHADOW_END2		15.110						# end of C21 planning interval.
setenv LRP_SHADOW_LRESADJ       c21_build_02_t03_adj_lt				# resource file used for Cycle 21 build.
setenv LRP_SHADOW_VRESADJ	reslimit_ultimate_flat_plus_tail_adj_val	# standard file used.  Normally should not change.
#
setenv LRP_SHADOW_ONOFF		ON						# controls whether shadow is on or off ON = on.
#										# set to other value such as OFF to disable shadow.
#
"""


Also check the following two envars to ensure they make sense:


setenv LRP_NEWCYCLE_CONTROL     lrp-control-file                        # control file for 'newcycle' batch jobs.
setenv LRP_NEWCYCLE_CRITERIA    build_c21_saaflex_and_np_on_GAon        # criteria file for newcycle batch jobs.


But this isn't all.  Even though we have 'enabled' the shadow process (triggered in the batch LRP), we need to 'tell' 
the shadow which build/twig to use.  This is done by 'emplacing' an LRP with the appropriate name.
Suppose we have decided that the C21B18T02L02 LRP is the one we wish to use from the build selection process.
We need to copy that LRP to one with a name similar in form to 'NT0411D12265'

This was the last Shadow LRP produced in Cycle 20.  Left to itself, though the shadow process
would not pick this lrp up because it was generated too far back in time, and instead malfunction.  This is because 
it relies on the tool `getlrpname -n` to identify the latest 'NT' shadow LRP to pull into the shadow process.
Running the tool at this time returns nothing.

We are going to copy the C21B18T02 LRP into such a name and try out the shadow.  July 24th is 13.205,
but the C21B18T02 LRP was created on July 21, so we are going to copy it to NT1802D13202 to prepare it
for use.


[lrp@daffy] /data/lrp/jordan 07-24 11:34> copy-lrp C21B18T02L02 NT1802D13202


Now running `getlrname -n` yields the name of the NT LRP we just created.


[jordan@quadrans] /data/lrp/cycle21 07-24 11:37> getlrpname -n
NT1802D13202


shadow.bash is invoked from within lrp-batch which is the 'batch lrp' script.
lrp-batch checks for the state of the envar LRP_SHADOW_ONOFF and if ON, 
runs the shadow; skips it if anything else.



 Deactivation of the shadow.

This is as simple as checking out ops-lrpg, setting the state of , and checking it back in.


uvm res ops-lrpg
edit ops-lrpg
	(set the state of LRP_SHADOW_ONOFF to 'OFF')
uvm rep ops-lrpg