Changes between Version 6 and Version 7 of Processing/IPASTC
- Timestamp:
- Jun 9, 2011, 3:06:04 PM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Processing/IPASTC
v6 v7 5 5 All files should be named according to the year, julian day and flight letter (where applicable) - YYYYJJJf.* 6 6 7 When you have found the best solution re-process the navigation to create a sol file for the RCD. Change the lever arm values to those for the RCD (given below) and the output sol file to *_camera.sol. 7 8 8 9 === Setting up the Project === … … 103 104 Lever arm values to enter into the software for 2011 onwards are: 104 105 106 107 For LiDAR processing: 108 105 109 || ||X ||Y ||Z || 106 110 ||GNSS ||-0.144|| -0.029|| -1.672|| … … 108 112 ||User Frame|| -0.142|| -0.001|| -0.188 || 109 113 114 110 115 These values are entered in the flight planning software and '''should''' automatically populate in IPAS. [[BR]] 111 116 The GNSS and IMU values can be changed in IPAS TC if they are incorrect. The user frame values cannot. They can be checked in ipas/extract/*extract.log. If you find these values are not correct let Ops know so they can change them to what they should be. 117 118 119 For processing the sol file for the RCD use the following lever arm values: 120 121 122 || ||X ||Y ||Z || 123 ||GNSS ||-0.256|| -0.090|| -1.612|| 124 ||IMU || -0.523|| 0.145|| -0.132 || 125 112 126 113 127 == Troubleshooting ==