Changes between Version 6 and Version 7 of FS Guide
- Timestamp:
- Jan 28, 2008, 11:04:32 PM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
FS Guide
v6 v7 5 5 6 6 Requirements 7 * Windows XP or Vista 8 * Microsoft .NET 2.0 (Use Windows update to install directly from Microsoft) 7 * Any PC running Microsoft .NET 2.0 (Use Windows update to install directly from Microsoft) 9 8 * 2 MB free harddisk space for FS itself, you might want some more for tracklogs and such. 9 It has been tested on Windows 2003 Server, Windows XP and Vista but (teoretically) it should work on any platform as long as .NET 2.0 is installed. 10 10 11 Download FS from here. You will get the file '''fssetup.exe''', run it. It will ask where you want to install FS. Make a folder somewhere on the disk and click OK. FS will then install itself in that folder you made. 11 12 Download FS from here: [CurrentVersion]. You will get the file '''fssetup.exe''', run it. It will ask where you want to install FS. Make a folder somewhere on the disk and click OK. FS will then install itself in that folder you made. 12 13 13 14 FS will not make any icons for now. In the FS folder you will find some useful programs that you can start directly. 14 15 * FSComp.exe - The main program for setting up and scoring a competiton 15 * FSFlight.exe - A tool for visualizing the tracklogs in a task (Very basic)16 * Participants.xlt - A MS Excel sheet for quick and easy registering of users. You need to have macros enabled in Excel.16 * Participants.xlt - A MS Excel template for quick and easy registering of users. You need to have macros enabled in Excel. 17 * lc.xls - A MS Excel workbook for viewing Leading Coefficient graphs. 17 18 18 19 === About the database and data === … … 26 27 Always keep a backup of your .fsdb file and tracklogs, especially after finalizing scores for one day. The data folder can be stored on a USB key for easy backup and transportation between computers. 27 28 28 === About the pilot ID and CIVL 29 === About the pilot ID and CIVLID === 29 30 30 31 The pilot ID is the unique number of the pilot in the competition. This must be unique and it will save you a lot of time to let the pilots in your clob or organization have the same number over time, as it's written to the GPS, and eventually you will remember each pilot's number. 31 32 32 The CIVL ID is just that, the number on the pilots licence. It's used when you run a Cat 2 or Cat 1 competition, and want to upload the results for the WPRS ranking points. 33 The CIVLID is the ID a pilot is given the first time he/she is registered in the CIVL database. 34 This will normally happen after one has been in a FAI Category 1 or 2 competition. 35 Any pilot that has been in a Cat 1 or 2 competition after 2001 should be in this database. 36 37 This ID is used when uploading results to the CIVL database where it is used to generate the World Ranking (WPRS). 33 38 34 39 === About the error margin when checking tracklog === … … 72 77 === Importing pilot lists from external sources === 73 78 74 If you have a RACE db or a !CompeGps .pil file with participants you can import pilots from these files using "Tools/Odds & Sods/Import pilotlist from ..." to initially populate the particpant list.79 If you have a RACE db or a CompeGps .pil file with participants you can import pilots from these files using "Tools/Usefull stuff/Import pilotlist from ..." to initially populate the particpant list. 75 80 76 If you have a bunch of tracklogs, you can use "Tools/ Odds & Sods/Create pilotlist from tracklogs".81 If you have a bunch of tracklogs, you can use "Tools/Usefull stuff/Create pilotlist from tracklogs". 77 82 The tracklogs must have file name as made by GpsDump in comp mode in order for it to make sense. Also no two tracklogs can have same id. 78 83 79 For any of the import options above any existing participants with same id as the imported ones will be replaced. 84 For any of the import options above only pilots having id not already in the fsdb will be imported. 85 In other words, all existing participants will stay as is. 80 86 81 87 == Tasks and task types == … … 104 110 === Task types === 105 111 106 Race with a single startgate: set which tp is start of speedsection (SS) and end of speedsection (ES) then add a single start gate.112 Race with a single startgate: Select task type "Race" and set which tp is start of speedsection (SS) and end of speedsection (ES) then add a single start gate. 107 113 108 Race with a multiple startgates: set which tp is start of speedsection (SS) and end of speedsection (ES) then add several start gates.114 Race with a multiple startgates: Select task type "Race" and set which tp is start of speedsection (SS) and end of speedsection (ES) then add several start gates. 109 115 110 Elapsed time race: set which tp is start of speedsection (SS) and end of speedsection (ES) but do not add any start gates.116 Elapsed time race: Select task type "Elapsed time" and set which tp is start of speedsection (SS) and end of speedsection (ES) but do not add any start gates. 111 117 112 118 Open distance: must have at least one tp. Can have more in which case it is "open dist via turnpoints". See futher description below. 113 119 120 Open distance on a heading: Same as open distance above, but check the "Heading" checkbox and add an extra turnpoint at the end which gives the heading to fly. 121 114 122 Race to nowhere: Set startpoint, start cyl, and a larger goal cyl around same TP. ES is when pilot cross out of goal cyl. 123 124 Lots of other variants of tasks is possible, tps with big or small cylinders, tps inside/outside each other, f.ex. one can fly from start out the edge of a 50km cylinder then back to start again ("Race to nowhere and back"). 125 115 126 116 127 == Waypoints == … … 132 143 Also GpsDump can of course read the waypoints from a GPS so as long as you are able to get your waypoints into a GPS somehow you're set. 133 144 134 In the Task window select "File/Open Waypoints file" to fill the Waypoints list.145 In the Task window click on the "Open waypoints file" to fill the Waypoints list. 135 146 136 Double-click on a waypoint to add it to the Turnpoints list and select a turnpoint then edit the details below and press "Set".147 Double-click (or select and press Enter or right-click...) on a waypoint to add it to the Turnpoints list. 137 148 138 Remove a turnpoint by selecting it then press the Delete key.139 Checking tracklogs etc.149 Edit a turnpoint double-click (or select and press Enter or right-click...). 150 Remove a turnpoint by selecting it then press the Delete key (or right-click...). 140 151 141 Select one or more rows in the grid (under the Task tab) then right-click and you get a menu with some choices... 152 == Checking tracklogs etc. == 142 153 143 After checking tracklogs, setting status for those not having tracklog, etc. you can select "Tasks/Score Task (GAP)" to create results, then produce reports with "Tasks/Task ..." 154 See popup-menus (right-click) in "Tasks" list and "Task participants" list. 155 For the "Task participants" list some of the menuitems work on the rows you selected. 156 157 After checking tracklogs, setting status for those not having tracklog, etc. you can produce reports from the "Reports" menu. 144 158 145 159 If a pilot got several tracklog files the one with last file modified timestamp is checked. 146 160 147 161 Note: nothing happens to the fsdb file itself until you save it ("File/Save Competition ..." where you get the option to specify filename). This means you can test different things and discard these by not saving before exiting the program. 148 Editing a task149 162 150 After editing a task one need to check tracklogs again. 163 == Editing a task == 164 165 After editing a task one may need to check tracklogs again. 151 166 152 167 Task validation and scoring is removed for all those that has tracklog and these rows get status NYP again. … … 154 169 Those pilots where one has entered distance or set status manually will keep their data. 155 170 156 This means one can sort the rows on the status column and mark those rows with status NYP and check tracklogs again .171 This means one can sort the rows on the status column and mark those rows with status NYP and check tracklogs again or use the menuitem "Check ... NYP". 157 172 158 173 Note: any penalties is also removed. … … 160 175 '''Open distance task''' 161 176 162 Add a n EXITturnpoint for take off (or where ever the start of the task should be from). Set open time for when the take off is open, Set close time for when the task closes, meaning tracklog-points after this time will not be checked. Set radius so that the circle covers a bit more than the take off. Note: As pilots often do not have valid tracklogpoints at take off it is possible to set an option to not check the take off turnpoint.177 Add a turnpoint for take off (or where ever the start of the task should be from). Set open time for when the take off is open, Set close time for when the task closes, meaning tracklog-points after this time will not be checked. Set radius so that the circle covers a bit more than the take off. Note: As pilots often do not have valid tracklogpoints at take off it is possible to set an option to not check the take off turnpoint. 163 178 164 If you want to have take off window close different from task close: Set a radius for take off turnpoint so that one can be sure pilots will have points inside after taking off. Add same turnpoint once more as EXIT. Set close time for when the task closes. Turn OFF option to not check the take off turnpoint. 165 Reporting 179 If you want to have take off window close different from task close: Set a radius for take off turnpoint so that one can be sure pilots will have points inside after taking off. Add same turnpoint once more. Set close time for when the task closes. Turn OFF option to not check the take off turnpoint. 166 180 167 181 == Reports == 168 182 169 Two report templates is included. "comp_result.xsl", and "task_result.xsl". These can be used from the "Reports" menu. 183 A set with default reports templates is included. One for task result (task_result.tkr.xsl), one for competition result (comp_result.cpr.xsl), one for team results (team_result.tmr.xsl), and one for participant list (participant_list.ptl.xsl). 184 These can be used from the respective menuitems under the "Reports" menu. 170 185 171 If they do not look the way you like (language etc...) just copy them to your comp folder and open them in a text editor and edit the content. This requires a little knowledge of xml so that one stay away from content that should not be changed. 172 173 There is also a simple html task report under the "Tasks" menu. 186 If they do not look the way you like (language etc...) just make a copy and open them in a text editor and edit the content. This requires a little knowledge of xml so that one stay away from content that should not be changed. 187 Note: Keep the extention (from the first .) the same.