PDG: Paths mapping parametes added to scheduler.

References: #514.

docs/software/houdini.rst

@@ -601,6 +601,16 @@ Scheduling Parameters
 	Specifies the directory where the cook generates intermediate files.
 	The intermediate files are placed in a subdirectory named ``pdgtemp``.
 
+- Path Mapping
+	- Global
+		If the PDG Path Map exists, then it is applied to file paths.
+	- None
+		Delocalizes paths using the PDG_DIR token.
+
+- Path Map Zone
+	When on, specifies a custom mapping zone to apply to all jobs executed by this scheduler. 
+	Otherwise, the local platform is ``LINUX``, ``MAC`` or ``WIN``.
+
 
 Submit Graph As Job
 -------------------
@@ -729,6 +739,11 @@ Adjustment Parameters
 	A cook that is blocked on failed work items can still be canceled using the ESC key,
 	the cancel button in the TOP task bar, or the cancel API method.
 
+- Validate Outputs When Recooking
+	When enabled, PDG will check the output files of work items when the graph recooks,
+	to see if the files still exist on disk.
+	Work items that are missing output files will be dirtied and cook again.
+
 - Check Expected Outputs On Disk
 	When enabled, PDG will look on disk for any expected work items outputs
 	that were not explicitly reported when the work item cooked.

plugins/houdini/pdg/types/afanasyscheduler.py

@@ -184,6 +184,12 @@ def _constructTask(self, work_item):
         task.setEnv('PDG_INDEX4', "{:04d}".format(work_item.index))
         task.setEnv('PDG_SCRIPTDIR', str(self.scriptDir(False)))
 
+        # This adds paths mapping data to environment
+        self.resolvePathMapping(task.data['environment'])
+        # We need to set it after task.setEnv,
+        # as on task.setEnv CGRU paths mapping applied.
+        # And better not to apply CGRU paths mapping on PDG paths mapping data.
+
         return task