Re: [Flightgear-devel] Aircraft Checklists
Stuart Thanks, that looks as if it will do my job. I will give it a go ASAP, probably at the weekend. BTW, I found a Flight article about our glass cockpit project http://www.flightglobal.com/pdfarchive/view/1977/1977%20-%201182.html. The checklist display can be seen on the extreme right hand CRT in the picture. It is described on page 3 of the article. Alan -Original Message- From: Stuart Buchanan Sent: Wednesday, February 27, 2013 10:33 PM To: FlightGear developers discussions Subject: Re: [Flightgear-devel] Aircraft Checklists On Mon, Feb 18, 2013 at 1:26 PM, Stuart Buchanan wrote: On Sun, Feb 17, 2013 at 11:56 PM, Alan Teeder wrote: The reason for my query was that I have found making a representative set of checklists is becoming very unwieldy. With just my entering the cockpit checks, I have already made 9 separate checklist. Each one has about 10 checks. I have made one checklist per check list card on the real aircraft. These checklist items disappear off the top of the menu list screen, and there is no indications as to which checklists/cards have been completed, or which is the next to do. Having got this far it is obvious that the current system will not cope for the rest of the aircraft checklists that I intend to replicate. OK, sounds like you've got much longer checklists than I have encountered myself. I'll see what I can do to support multi-page checklists. I can probably add Next and Previous buttons to page through the checklist. This is now available. item nodes can now be grouped under a page, which the checklist display handles as you would expect. I've also added support for marker tags which leverage the existing tutorial markers. I've updated Docs/README.checklist and the wiki to reflect both these changes. As always, the c172p has an example (Aircraft/c172p/c172-checklists.xml). I've still to update the checklist-tutorial converter to support the tags - that's next on my TODO list. -Stuart -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Aircraft Checklists
On Mon, Feb 18, 2013 at 1:26 PM, Stuart Buchanan wrote: On Sun, Feb 17, 2013 at 11:56 PM, Alan Teeder wrote: The reason for my query was that I have found making a representative set of checklists is becoming very unwieldy. With just my entering the cockpit checks, I have already made 9 separate checklist. Each one has about 10 checks. I have made one checklist per check list card on the real aircraft. These checklist items disappear off the top of the menu list screen, and there is no indications as to which checklists/cards have been completed, or which is the next to do. Having got this far it is obvious that the current system will not cope for the rest of the aircraft checklists that I intend to replicate. OK, sounds like you've got much longer checklists than I have encountered myself. I'll see what I can do to support multi-page checklists. I can probably add Next and Previous buttons to page through the checklist. This is now available. item nodes can now be grouped under a page, which the checklist display handles as you would expect. I've also added support for marker tags which leverage the existing tutorial markers. I've updated Docs/README.checklist and the wiki to reflect both these changes. As always, the c172p has an example (Aircraft/c172p/c172-checklists.xml). I've still to update the checklist-tutorial converter to support the tags - that's next on my TODO list. -Stuart -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Aircraft Checklists
On Sun, Feb 17, 2013 at 11:56 PM, Alan Teeder wrote: The reason for my query was that I have found making a representative set of checklists is becoming very unwieldy. With just my entering the cockpit checks, I have already made 9 separate checklist. Each one has about 10 checks. I have made one checklist per check list card on the real aircraft. These checklist items disappear off the top of the menu list screen, and there is no indications as to which checklists/cards have been completed, or which is the next to do. Having got this far it is obvious that the current system will not cope for the rest of the aircraft checklists that I intend to replicate. OK, sounds like you've got much longer checklists than I have encountered myself. I'll see what I can do to support multi-page checklists. I can probably add Next and Previous buttons to page through the checklist. One question: Would you prefer that the UI itself split the checklist up, or for the checklist author to do it themselves? The former would be automatic, but wouldn't allow the author to place the page-break where they wished. Yes, my level of simulation will include such detail as the fail to relight in 20 seconds scenario. Very good :) For background info my suggestions were based upon an interactive checklist system that I was involved with in the 1980´s as part of a joint BAC/Hawker Siddeley glass cockpit simulation. This was before the two companies merged to form BAe. AFAIK this was the first glass cockpit project to have an in depth simulator evaluation. Our two target aircraft were the VC10 ( completely eliminating the flight engineer station) and the A300 which was state of the art at that time. This electronic checklist also bought up the relevant systems displays on one or more other front panel CRT´s . In normal use (e.g. start-up) the electronic checklist was selected by the crew, but the relevant set of checks were automatically initiated when aircraft failures were detected. The system was intelligent enough to follow the sequence of events following an emergency (e.g. my relight scenario) , and also had a priority system to deal with the major faults (engine failure, fire, etc) before lesser ones. At the moment my TSR2 is not a glass cockpit, but having a usable checklist system would save a lot of paper. AS an old fogey I am not up to speed with current developments in this field, but am sure that some of our work has a modern counterpart. Yup, and I think that would be the glass cockpit of the aircraft itself rather than the simulator UI. Anyway - you asked for comments on your checklist system ;) Yup, and very good feedback it is as well. Thanks. -Stuart -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Aircraft Checklists
Stuart. Just came in from the garden and saw your reply. In real life checklists get much, much more complicated when he aircraft has systems. A glider or a basic Cessna will be quite simple. I would prefer that the author can add his own page breaks. The checklist cards that I working on at the moment are organised in that manner. For example my Entering Cockpit checklist is split into 9 separate cards, which are meant to be used in a left to right order - starting with the rear left hand console panel, working forwards to the instrument panels and the rearwards along the right hand console. There is one card per panel. The take-off, engine start and other drills are similarly split into logical sections. Yes, our simulator had visits from Boeing and other overseas companies. We displayed at Farnborough and on BBC TV. As you know, the VC10 was the last large aircraft that was a solely UK project. This simulator was built to a systems training simulator standard, which made it practically the same as a full simulator , but without visual or motion systems. I was given a PDP 11/45, practically fully expanded and costing about 100,000$, to host the FDM, autopilot and navigation. A second team had a PDP11/20 and a PDP 11/05 to handle the systems (including checklists) and drive the CRT display hardware. Prices and computer power have changed since then. Alan -Original Message- From: Stuart Buchanan Sent: Monday, February 18, 2013 1:26 PM To: FlightGear developers discussions Subject: Re: [Flightgear-devel] Aircraft Checklists On Sun, Feb 17, 2013 at 11:56 PM, Alan Teeder wrote: The reason for my query was that I have found making a representative set of checklists is becoming very unwieldy. With just my entering the cockpit checks, I have already made 9 separate checklist. Each one has about 10 checks. I have made one checklist per check list card on the real aircraft. These checklist items disappear off the top of the menu list screen, and there is no indications as to which checklists/cards have been completed, or which is the next to do. Having got this far it is obvious that the current system will not cope for the rest of the aircraft checklists that I intend to replicate. OK, sounds like you've got much longer checklists than I have encountered myself. I'll see what I can do to support multi-page checklists. I can probably add Next and Previous buttons to page through the checklist. One question: Would you prefer that the UI itself split the checklist up, or for the checklist author to do it themselves? The former would be automatic, but wouldn't allow the author to place the page-break where they wished. Yes, my level of simulation will include such detail as the fail to relight in 20 seconds scenario. Very good :) For background info my suggestions were based upon an interactive checklist system that I was involved with in the 1980´s as part of a joint BAC/Hawker Siddeley glass cockpit simulation. This was before the two companies merged to form BAe. AFAIK this was the first glass cockpit project to have an in depth simulator evaluation. Our two target aircraft were the VC10 ( completely eliminating the flight engineer station) and the A300 which was state of the art at that time. This electronic checklist also bought up the relevant systems displays on one or more other front panel CRT´s . In normal use (e.g. start-up) the electronic checklist was selected by the crew, but the relevant set of checks were automatically initiated when aircraft failures were detected. The system was intelligent enough to follow the sequence of events following an emergency (e.g. my relight scenario) , and also had a priority system to deal with the major faults (engine failure, fire, etc) before lesser ones. At the moment my TSR2 is not a glass cockpit, but having a usable checklist system would save a lot of paper. AS an old fogey I am not up to speed with current developments in this field, but am sure that some of our work has a modern counterpart. Yup, and I think that would be the glass cockpit of the aircraft itself rather than the simulator UI. Anyway - you asked for comments on your checklist system ;) Yup, and very good feedback it is as well. Thanks. -Stuart -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Aircraft Checklists
On Fri, Feb 15, 2013 at 9:23 PM, Alan Teeder wrote: Is there any way to chain checklists automatically so that they follow one another in a pre-defined order? They should appear in the checklists dialog in the order in which they are defined in the XML file, so simply define them in the order you wish. An alternative, which may have further advantages, would be to have a tree structure of checklists, where one branch has to be completed before going back to the trunk and then on to the next branch. Note that the checklist function doesn't enforce any action on the part of the pilot. It simply provides a convenient representation of a textual checklist plus some highlighting to indicate completed steps and (once I get around to it) the ability to highlight the relevant controls. e.g. on cockpit entry I want to do a right to left sequence of checks, starting with the port side panel, going on to the port coaming, then the port instrument panel etc, covering the whole cockpit methodically. Each of these panels has up to a dozen checks. This is how the checks were actually organised (with a book of cards) on this particular aircraft. The cockpit entry checks were then followed by the start sequence, the after starting, the take off, after take-off, circuit ad approach /landing checks. I don't think that's a tree structure, just an ordered list, which is already provided. The emergency checks also follow a tree structure, but in this case the next branch depends upon the result of a particular check. (e.g. did the engine relight within 20 seconds?) I think that's getting a bit specialized, and overly complicated. I'd also point out that we're just supporting the pilot's use of checklists, not attempting to automate them. I don't think it's unreasonable to have a checklist items that says if the engine does not relight within 20 seconds, run the Engine Dead Checklist (Additionally I'd be pleasantly surprised if our systems/failure modelling is good enough that such a decision tree wouldn't always go down the same path.) -Stuart -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Aircraft Checklists
-Original Message- From: Stuart Buchanan Sent: Sunday, February 17, 2013 8:31 PM To: FlightGear developers discussions Subject: Re: [Flightgear-devel] Aircraft Checklists On Fri, Feb 15, 2013 at 9:23 PM, Alan Teeder wrote: Is there any way to chain checklists automatically so that they follow one another in a pre-defined order? They should appear in the checklists dialog in the order in which they are defined in the XML file, so simply define them in the order you wish. An alternative, which may have further advantages, would be to have a tree structure of checklists, where one branch has to be completed before going back to the trunk and then on to the next branch. Note that the checklist function doesn't enforce any action on the part of the pilot. It simply provides a convenient representation of a textual checklist plus some highlighting to indicate completed steps and (once I get around to it) the ability to highlight the relevant controls. e.g. on cockpit entry I want to do a right to left sequence of checks, starting with the port side panel, going on to the port coaming, then the port instrument panel etc, covering the whole cockpit methodically. Each of these panels has up to a dozen checks. This is how the checks were actually organised (with a book of cards) on this particular aircraft. The cockpit entry checks were then followed by the start sequence, the after starting, the take off, after take-off, circuit ad approach /landing checks. I don't think that's a tree structure, just an ordered list, which is already provided. The emergency checks also follow a tree structure, but in this case the next branch depends upon the result of a particular check. (e.g. did the engine relight within 20 seconds?) I think that's getting a bit specialized, and overly complicated. I'd also point out that we're just supporting the pilot's use of checklists, not attempting to automate them. I don't think it's unreasonable to have a checklist items that says if the engine does not relight within 20 seconds, run the Engine Dead Checklist (Additionally I'd be pleasantly surprised if our systems/failure modelling is good enough that such a decision tree wouldn't always go down the same path.) -Stuart Stuart Thanks for the reply. The reason for my query was that I have found making a representative set of checklists is becoming very unwieldy. With just my entering the cockpit checks, I have already made 9 separate checklist. Each one has about 10 checks. I have made one checklist per check list card on the real aircraft. These checklist items disappear off the top of the menu list screen, and there is no indications as to which checklists/cards have been completed, or which is the next to do. Having got this far it is obvious that the current system will not cope for the rest of the aircraft checklists that I intend to replicate. Yes, my level of simulation will include such detail as the fail to relight in 20 seconds scenario. For background info my suggestions were based upon an interactive checklist system that I was involved with in the 1980´s as part of a joint BAC/Hawker Siddeley glass cockpit simulation. This was before the two companies merged to form BAe. AFAIK this was the first glass cockpit project to have an in depth simulator evaluation. Our two target aircraft were the VC10 ( completely eliminating the flight engineer station) and the A300 which was state of the art at that time. This electronic checklist also bought up the relevant systems displays on one or more other front panel CRT´s . In normal use (e.g. start-up) the electronic checklist was selected by the crew, but the relevant set of checks were automatically initiated when aircraft failures were detected. The system was intelligent enough to follow the sequence of events following an emergency (e.g. my relight scenario) , and also had a priority system to deal with the major faults (engine failure, fire, etc) before lesser ones. At the moment my TSR2 is not a glass cockpit, but having a usable checklist system would save a lot of paper. AS an old fogey I am not up to speed with current developments in this field, but am sure that some of our work has a modern counterpart. Anyway - you asked for comments on your checklist system ;) Alan -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo
[Flightgear-devel] Aircraft Checklists
Hi All, Inspired by the checklists provided for the excellent Cessna 337, I've added generic checklist support to the GUI. The GUI element is pretty straightforward, with a drop-down to select a checklist and the checklist displayed as one would expect: http://wiki.flightgear.org/File:Aircraft_Checklists_dialog.jpg Aircraft developers can simply add checklists by setting up properties under /sim/checklists. This is documented in this wiki article: http://wiki.flightgear.org/Aircraft_Checklists, and the c172p now includes and example. I think this provides a much easier way to navigate and display checklists than over-loading the Aircraft Help dialog, as well as taking up minimal screen real-estate. Hopefully as we move to using Canvas in the future we'll be able to improve the checklist display to include a set of dots linking the items. Feedback and comments are welcome as always, particularly if any aircraft developers would like any enhancements made. -Stuart -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Aircraft Checklists
On 18 Sep 2012, at 11:56, Stuart Buchanan wrote: Feedback and comments are welcome as always, particularly if any aircraft developers would like any enhancements made. Fantastic! James -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
