-------------------------------------------------------- -------------------------------------------------------- NPB Release 1 Procedure -------------------------------------------------------- -------------------------------------------------------- NPB Setup - Using InSight as an example - Release 1 Linux/Mac - using c-shell terminal/command line Windows - using Windows Subsystem for Linux (WSL) with c-shell -------------------------------------------------------- * Set up the directories - insight/ - empty staging/ - empty kernels/ - has all of the new kernels in kernel type subdirectories working/ - has the NPB config and release 1 plan working/document/ - has readme.txt and archive description file -------------------------------------------------------- * Make the release plan - Note - Order does not matter List the kernels for this release including the next MK -> however NPB will make the MK for you For release 1 it will be named - insight_release_01.plan ex. insight_release_01.plan file_lsk.tls file_pck.tpc file_sclk.tsc file_spk.bsp file_monthly_spk.bsp file_monthly_ck.bc file_mk.tm -------------------------------------------------------- * Make version 1 of the SPICE archive description (spiceds) html file Example of needed updates - - New types of files - Ex. Adding DSKs when there previously weren't any - Ex. Adding new SPKs with a new naming scheme - Etc.. - New Errata items - Missing files - Missing data - loss of coverage due to safe mode - Etc.. -------------------------------------------------------- * Make the NPB configuration file For release 1 it will be named - insight_release_01.xml Make sure the directory paths are set to your working area and that all kernel patterns are set properly. Check the Meta-Kernel is setup the way you want. -> Have 'interrupt_to_update' set to 'true' True This will allow you to look at the MetaKernel and make any needed updates after NPB has created the file and before it finishes running! -------------------------------------------------------- Running NPB for Release 1 -------------------------------------------------------- In your top level directory that contains the working/ staging/ etc... set your release variable - % set REL = 01 % echo $REL -------------------------------------------------------- Source your NPB virtual environment ex. % source ~/virtenvs/npb/bin/activate.csh % source /mnt/c/Users/abailey/virtenvs/npb/bin/activate.csh -------------------------------------------------------- * Run a test/staging run to catch any issues initially - '-p' plan file '-l' output a log file '-v' verbose - prints full log during execution '-f staging' ends pipeline at staging % naif-pds4-bundler working/insight_release_"$REL".xml -p working/insight_release_"$REL".plan -l -v -f staging -> Check the log for any errors and read through all warnings! less working/insight_release_"$REL".log grep -E 'WARNING' working/insight_release_$REL.log grep -E 'ERROR' working/insight_release_$REL.log -> Clear the staging run files '-c file.file_list' clears files from staging and bundle as generated by the file_list % naif-pds4-bundler working/insight_release_"$REL".xml -c working/insight_release_"$REL".file_list -l -v Check to be sure this cleared out the directories in staging -> Clean up working - Make sure to keep the plan and config files!! remove the release 1 files files NPB made insight_release_01.checksum insight_release_01.file_list insight_release_01.kernel_list insight_release_01.log insight_release_01.validate_config Ex. % rm insight_release_01.checksum insight_release_01.file_list insight_release_01.kernel_list insight_release_01.log insight_release_01.validate_config -------------------------------------------------------- * Run NPB for REAL! - This will create the archive bundle! % naif-pds4-bundler working/insight_release_"$REL".xml -p working/insight_release_"$REL".plan -l -v -> Inspect the NPB execution -> Check the log for any errors and read through all warnings! check the errors and warnings less working/insight_release_"$REL".log grep -E 'WARNING' working/insight_release_$REL.log grep -E 'ERROR' working/insight_release_$REL.log -------------------------------------------------------- Run the PDS4 Validate Tool! -------------------------------------------------------- Run validate on the complete bundle in the insight/ directory! % validate insight/insight_spice -c working/insight_release_$REL.validate_config -R pds4.bundle -r working/validate_"$REL"_report_`date +'%Y-%m-%d'`.txt View the report and address any errors! * The report must show all products 'passed' -------------------------------------------------------- Run SPICE Checks! -------------------------------------------------------- Validate the bundle with SPICE checks! * Examples of how you can validate using the MK % set MK = insight_v01.tm Shows SPK Coverage for all files ( -a) , center of motion (-c), in UTC (-utc) , tabular format (-t) % brief -a -t -c -utc $MK Shows SPK coverage for insight Spacecraft % brief $MK -a -t -utc --155 Displays all CK frames (-a) with frame names (-n) in tabular format (-t) in UTC (-utc) relative to other frames (-rel) % ckbrief -a -t -rel -n -utc $MK Checks for gaps in CK coverage % frmdiff -k $MK -t dumpg -f1 J2000 -t1 insight_SPACECRAFT -f YYYY-MM-DDTHR:MN:SC ::RND -------------------------------------------------------- END.