BUG? Missing Flights From Time Table Data Import

[sawblade5]

What about the balance of my post. Unless I know exactly what you are missing and the settings you used, there's not much I can do.

Don

I had to take sometime to put it together it took me almost 2 hours to do and I ran into some bugs trying to get em. One causing the wrong day to show up at certain airports such as KDTW which I noted mostly. Also for some strange reason I am getting crashes when I look at the time table through the "Traffic and Parking Analyser" (you can reproduce this by Clock in the Time Table Function and clicking on another airport (The Crash is seemingly random so you may have to click through more airports until you get it) The crash was detected when I used my Time Table Data here. Along with the previously mention Bug in the Regular Time Table where there's no Flights to a certain airport, It wreck havoc on trying to produce the data here.

Anyway the missing Flights are attached here All Flights are Daily unless noted:
Col 1 is From
Col 2 is To
Col 3 is Flight Number
Col 4 is Days Believed to be Missing as shown on the Time Table in the Program. (It may be different as a bug can make it show the wrong days and it affected KDTW mostly) (1 is Mon-7 is Sun)
Col 5 is Additional Notes like Days the Flight Runs. Rather or not it's a Red Eye (Next day arrival but I called them Red Eye even though they are probably not). Bug Notes, and other items that may be noteworthy. The numbers in there indicate affected days or days the flight runs on. (1 is Mon-7 is Sun)

They may be other missing flights I couldn't find as some only operate a few days a week ad all those flights could be missing and be a missing flight number from the time table. I caught a few of these but some may be hiding from me though I am sure I got at least 99% of them. I noted the flights that I did manage to spot in the file.

The Airport that seems to have the most missing FPs by a seemingly large margin is KFLL which is their main hub.It would be a good place to start looking for the cause at since it was the cause of many missing flight numbers and airports as noted above.

Hopefully you can find a pattern and fix the bugs.

 

[gadgets]

sawblade5. Please read carefully.

I can tell by inspection what columns in your timetable data serve which purpose. What I need from you is a flight plan file set or a traffic file prepared from that data that causes the exceptions in the Timetable display. As I have said repeatedly, I am unable to reproduce such errors with the data, i.e., flight plans/traffic files, at hand. I'm not surprised the same issue occurs in the Traffic Analyser. For the most part, the two Timetable functions use common code.

I also asked you to specify the parameters you were using in creating the flight plans in which you claim there are missing airports and to specifically identify which legs are missing. While I appreciate you identifying every missing leg, (I only needed one or two) I still need to know the parameters you were using to generate those flightplans. It's highly unlikely I can fix something I can't duplicate.

Finally, please appreciate that the selection of Local Time or a specific timezone will cause significant differences in what you see. That would appear to be a potential cause of some of the things you are reporting as errors.

These are simple requests. Without that data/information I have no basis on which to test.

Don

 

[gadgets]

The only things I received from you yesterday was a dump of the flight plan validation report and the original timetable text data.

What I need is the flight plan file set or traffic file you prepared from the timetable text data and the parameters you used to generate it.

Don

 

[gadgets]

Ok. I've now received the flight plan file set. That's progress. Now, if you would tell me the parameters you used to generate it and, regarding the exception, which flight plan number you were displaying, I can start to investigate (Telling me what airport you were looking at at the time is of little use if I don't know which flight plan was displayed.)

Don

 

[sawblade5]

I also asked you to specify the parameters you were using in creating the flight plans in which you claim there are missing airports and to specifically identify which legs are missing. While I appreciate you identifying every missing leg, (I only needed one or two) I still need to know the parameters you were using to generate those flightplans. It's highly unlikely I can fix something I can't duplicate.

Don

Already been sent to ya again. I thought you had those yesterday!

The only things I received from you yesterday was a dump of the flight plan validation report and the original timetable text data.

What I need is the flight plan file set or traffic file you prepared from the timetable text data and the parameters you used to generate it.

Don

Done, Check the attachments for a screen cap of my parameters in your PM. As for the Flight Plan File Set. Some of the errors do disappear when you load it as the missing airports that flight plans were supposed to included for are missing and therefore the error will only show up when you load form the time table data.

So to reproduce the error on your end.

1 Open Time Table Data and select the Spirit AirlinesfullC.txt I sent and use the import parameters as you see attached in your DM or here and import it.

2. You should now have the flight plans loaded up now

3. Now that you have them loaded up go under the Flight Plans Menu and Select Time Table

4. Under the Time Table menu and select one of these airports: MHLM, MPTO, SKRG, or TNCA

5. The error box should pop up now.

I also just discovered a way to reproduce the same error using any other flight plan.

1. Open any flight plan file set or bgl file.

2. Highlight all the FPs in there except for one.

3. Now go under the Time Table menu and select random airports or just scroll down the list. You should be able to run into the same error as produced above.

I also noticed an unrelated error that is caused when you deleted too many legs from a leg editor at once.

1. Open any flight plan file set or bgl file.

2. Find a FP with quite a few Legs on it.

3. Highlight it and open the Leg Editor

4. Inside the Leg Editor Highlight all the flight legs except for a few.

5. Now delete them by clicking on Delete Legs.

6. The error should pop up then. If not close out the leg editor and find another FP and go from step 1 again.

Now let me know if you are still having trouble finding the missing FPs from the original error that caused me to start this thread.

 

[gadgets]

Lets do this one step at a time.

• When I ask for the parameters, I'm looking for sit time, the type of timetable you created and whether or not you had asked for deadhead legs.
• I asked you which flight plan was selected when you experienced the timetable exception. What I'm after is, before you proceed with the first step 3 above, what flight plan in the Flight Plan List was selected. If I don't know that, I'm going to have to examine each of the 58 flight plans and click on each of four airports each time to see which one caused the error. That's over 200 operations. You can cut that to one by simply answering my question.

Before you go off looking for other error, lets get this one fixed. Chances are the other error you identified are a direct result of whatever is happening in the first place.

Don

 

[gadgets]

Some good news for a change. Once I saw how you created the file set, I was able to isolate the problem about "departure before arrival" in about two minutes. It was due to a line of code I had disabled in earlier testing and had neglected to re-enable.

I expect to be able to isolate and fix the exception just as quickly once I know what flight plan you were looking at.

Don

 

[sawblade5]

Lets do this one step at a time.

• When I ask for the parameters, I'm looking for sit time, the type of timetable you created and whether or not you had asked for deadhead legs.
• I asked you which flight plan was selected when you experienced the timetable exception. What I'm after is, before you proceed with the first step 3 above, what flight plan in the Flight Plan List was selected. If I don't know that, I'm going to have to examine each of the 58 flight plans and click on each of four airports each time to see which one caused the error. That's over 200 operations. You can cut that to one by simply answering my question.

Before you go off looking for other error, lets get this one fixed. Chances are the other error you identified are a direct result of whatever is happening in the first place.

Don

The error does not show up when I load the Flight Plan File Set. (I checked) But it does Show Up when I load it from the Time Table Data (Yes it's there) My Timezone is set as Local (which is the Central Time Zone where my local is but I don't have Central Set I have Local Set) and Standard is currently selected

IT is a FP from KTPA to KDTW and the Flight Number is 646. (You can find it in the Time Table Data) The Flight Leaves Tampa at 1935 and arrives at Detroit at 2158 and the flight is on days 1356 (Mon Weds Fri Sat) The flight will appear as going on Tues, Thurs, Sat (When in reality it is and in the FPs it shows Mon, Weds, Fri with the Saturday Flight missing)

When I had click on the Time table for Flight 646 it brought up Flight Plan #51 and it shows that Leg #17 is on Wednesday instead of what it shows as Thursday in the Time Table.

I hope that is what you are looking for do I still need to dig up the other 1 or 2 FPs that has the Monday or Friday legs?

 

[sawblade5]

BTW The other 2 I managed to figure out how to dig em up quickly for the TPS to DTW flight are Monday (Shows as Tuesday on the Time Table) are FP 50 Leg 11 per File Ref and Friday (Show as Sat in TT) FP 49 Leg 24 per File Ref. There's a missing flight for Saturday that did not import from the time table data.

Hopefully the one thing you just found will help get rid of a bunch of missing FPs. Let me know when you put out a fix for that.

 

[gadgets]

The error does not show up when I load the Flight Plan File Set. (I checked) But it does Show Up when I load it from the Time Table Data

Not clear how this could happen, since (presumably) its the same data. But, just to make sure its not an error based on another error, I have just uploaded Development Release 3.1.11(d) to http://stuff4fs.com. It addresses the numerous "departure before arrivals" issue and well as the new issue you reported a couple days ago when you edited with the text editor.

Please re-run your tests with the update. If there are still remaining issues, you now know what I need to have/know to address them.

To avoid complicating things, I also suggest you turn off Test Sit Times until we're sure the data generated for a single sit time is right

Don

 

[sawblade5]

All righty updated to D and reran. I am now running into an error for Flight 646, It is still showing the wrong day and now I am getting this lovely error box to go with it. This occurs when I highlight 646 as a departure from KTPA to KDTW under the KTPA time table. I have attached a screen shot of the error box showing where it happened at. Like wise on the Arrival side under the KDTW Time Table I do not get the error box but it still shows the wrong days for Flight 646 from KTPA.

To reproduce this one:

1 Open Time Table Data and select the Spirit AirlinesfullC.txt I sent and use the import parameters as you see at http://www.fsdeveloper.com/forum/attachments/parameters-png.23158/ here with the exception of Test Sit Times being unchecked and Same Flight Number Priority being 240 and import it or open the Flightplans_spiritbeta2.txt I sent ya.

2. Once Imported or opened go into the time table under the Flight Plans Menu.

3. Once in there go to the KTPA time table (You should now see the wrong days for Flight 646 to KDTW still sitting there but this time all 4 flights are there it just showing as the wrong day in the Time Table There! :>)

4. Now highlight Flight 646 to KDTW under the departures menu. The error box should pop up now.

Note: This error box will also pop up if you select flight 942 to KATL. The way the error box pops up you can't really get rid of it very easily without closing the program (You have to click hitting continue and select another airport once you can get out of the error boxes)

I am still missing a few flights like Flight 913 from KDTW to KMCI for 7 Sun and Flight 913 for KMCI to KDFW for 7 Sun. I will be working on a full dump for all missing flights but there's way fewer missing flights now. We have reverted back to square one as the first fix made it worse. Also still getting errors for Departure scheduled before or very close to arrival time of previous leg and The total duration of this flight plan exceeds the selected repeat period I will send ya the Flight Plan file set right away so you can review those errors.


I am still getting errors on deleting a bunch of legs from a fp at once you can recreate it using my existing time table dump or any file you please and follow the instructions to reproduce: (This error also seems to appear at times when I am deleting a bunch of FPs instead of going into the leg editor and deleting a bunch of legs)

1. Open any flight plan file set or bgl file.

2. Find a FP with quite a few Legs on it.

3. Highlight it and open the Leg Editor

4. Inside the Leg Editor Highlight all the flight legs except for a few.

5. Now delete them by clicking on Delete Legs.

6. The error should pop up then. If not close out the leg editor and find another FP and go from step 1 again.


For the Time Table error box. It is gone from the load up but I can still reproduce it going into these steps and it will create it if I hit continue the arrival side will stay blank after hitting continue on the error box.

1. Open any flight plan file set or bgl file.

2. Highlight all the FPs in there except for one.(Take note of the remaining airports)

3. Now go under the Time Table and select random airports or just scroll down the list. You should be able to run into the same error as produced above.

4 Hit Continue on the error box.

5. Now go highlight an airport that you took note of still being there from your remaining flight plans. The other error should show now where The Departure Side should shows some Flights wile the Arrival Side is Blank.

So right now the biggest error is that new error box error in the first part. The Missing FPs are much fewer but still there and causing certain issues. I will be sending ya the new Flight Plan file set I produced in Dev Version D there.

 

[gadgets]

I am now running into an error for Flight 646, It is still showing the wrong day

At least we know that error is not connected to the previous issue of "departure before arrival" - which I presume you are no longer encountering. That being the case, I can now investigate. BTW, when you report these things, it would be helpful to mention How it is wrong, e.g., what you expected and what you got. Otherwise, I have to guess.

and now I am getting this lovely error box to go with it

That's the same issue as you had before

2. Once Imported or opened go into the time table under the Flight Plans Menu

Again, it would be very helpful if you told me which of the 70-odd flight plans was selected when you called for the time table. All the data in the timetable pertains to the selected flight plan(s). Giving me a flight number isn't much help because that flight number could be repeated in several flight plans and, in any case, I have no easy way of relating flight number to flight pan.

I am still getting errors on deleting a bunch of legs from a fp at once you can recreate it using my existing time table dump or any file you please and follow the instructions to reproduce: (This error also seems to appear at times when I am deleting a bunch of FPs instead of going into the leg editor and deleting a bunch of legs)

I'll investigate.

1. Open any flight plan file set or bgl file.
6. The error should pop up then. If not close out the leg editor and find another FP and go from step 1 again

These sort of suggestions aren't helpful - especially when I've told you I am unable to repeat with my own test data. If you have a file and a set of circumstances that can reliably reproduce the error, send me the file and the details.

Don

 

[sawblade5]

At least we know that error is not connected to the previous issue of "departure before arrival" - which I presume you are no longer encountering. That being the case, I can now investigate. BTW, when you report these things, it would be helpful to mention How it is wrong, e.g., what you expected and what you got. Otherwise, I have to guess.

That's the same issue as you had before

Nope that is a new error showing up in this version to go on top of the old error. So we got 2 bugs here now.

Again, it would be very helpful if you told me which of the 70-odd flight plans was selected when you called for the time table. All the data in the timetable pertains to the selected flight plan(s). Giving me a flight number isn't much help because that flight number could be repeated in several flight plans and, in any case, I have no easy way of relating flight number to flight pan.

You don't have to go through the 70-odd flight plans or open any flight plans directly to find this bug. I have to flight number and Airport You need to highlight in the instructions Please reread the steps. Flight 646 is from KTPA to KDTW so if you goto the KTPA Time Table you will find it.

1 Open the Flightplans_spiritbeta2.txt I sent ya.

2. Once opened go into the time table under the Flight Plans Menu.

3. Once in there go to the KTPA time table (You should now see the wrong days for Flight 646 to KDTW still sitting there but this time all 4 flights are there it just showing as the wrong day in the Time Table There! :>)

4. Now highlight Flight 646 which is the flight from KTPA to KDTW under the departures menu. The error box should pop up now.

5. That error box will keep popping up after you hit continue if you hover your mouse over the departure side unless you change the airport in the Time Table menu.

These sort of suggestions aren't helpful - especially when I've told you I am unable to repeat with my own test data. If you have a file and a set of circumstances that can reliably reproduce the error, send me the file and the details.

Don

These bugs below can occur with any Flight Plan File Set but to simplify things and to reproduce exactly like I did. Just use the Flight Plan file set I sent ya and follow the steps.

1. Open the Flightplans_spiritbeta2.txt I sent ya.

2. Go to FP #69

3. Highlight it and open the Leg Editor

4. Inside the Leg Editor Highlight all the flight legs except for leg 1

5. Now delete them by clicking on Delete Legs.

6. The error should pop up then. It did for me.

As with the Time Table Error you didn't quote I rewrote so you can use my file

For the Time Table error box. It is gone from the load up but I can still reproduce it going into these steps and it will create it if I hit continue the arrival side will stay blank after hitting continue on the error box.

1. Open the Flightplans_spiritbeta2.txt I sent ya.

2. Highlight all the FPs in there except for FP 1.

3. Delete those FPs all at once.

4. If you get an error box and you probably will, hit continue and Highlight all the FPs except for #1 and delete them. (basically do steps 2-3 again) Otherwise proceed to the next step

5. Now go under the Time Table and select the first airport which should be KACY. You should/will encounter another error box.

6 Hit Continue on the error box.

7. Now select KLAS under Airports in middle box of the Time Tables Window. Another bug should appear caused from the error leaving the Arrival Side of the Time Table window blank with The Departure Side showing a Flight 208 to KDFW. (You can look at KDFW if you need for further verification of this bug)

Hopefully you understand these better as I hopefully gien the instructions on how exactly I reproduced these errors.

 

[gadgets]

We don't seem to be communicating. So let's end this discussion. I will continue to investigate the issues you have reported as time permits. If and when I find their cause, I will include the fixes in a new release and will announce it in the top sticky in this forum.

Don

 

[sawblade5]

OK, Let me know when you make an update.

I should had probably created separate threads for all those different bugs.

 

[gadgets]

I made the new release yesterday. It was announced in the top thread in this forum.

Don

 

[sawblade5]

Yep still missing a few flights and getting overlaps. What information right now do I need to help you smash this bug?

I don't know how this program compiles my Time Table data and why it skips some flights when it should be including it.

I am gonna toy around with giving my FPs Sit Times to see if I can somehow work around this. I know that in the past when I separated the aircraft type it worked well at least for the A319. (I need to test it on 320s and 321s)

BTW what is the default Sit Time if I do not specify one?

 

[gadgets]

The Timetable is displaying what's in the Flight Plan List. If the timetable is not showing a particular leg, then the leg almost certainly wasn't generated.

This situation is most likely to occur for the first and last legs in a flight plan when the flight plan is not circular, i.e., a deadhead leg was not added when needed. So, when a leg is missing, close the Timetable and analyse the flightplan that should contain that leg. If you don't have deadhead legs added when necessary, some legs WILL be missing.

The information I need is the same information I've always asked for, i.e.,

• the flight plan file set or traffic file containing the (problematic) flightplans created from the timetable data,
• the settings of the bottom-most controls on the Open Timetable Data File dialog;
• some identification of specific leg that is missing or that is overlapped - origin, destination, time, day of week (The data you were using last week creates over 160 flight plans with an average of 30 legs each. (I'm not about to check nearly 20,000 legs looking for a problem you have already identified.)

Also, please recognize that the Timetable display will be quite different depending on whether or not local time is selected.

Don

 

[sawblade5]

I have a few questions on this

The Timetable is displaying what's in the Flight Plan List. If the timetable is not showing a particular leg, then the leg almost certainly wasn't generated.

The information I need is the same information I've always asked for, i.e.,

• the flight plan file set or traffic file containing the (problematic) flightplans created from the timetable data,

Do you also want the Time Table data also or just the flight plan file set or traffic file?

• the settings of the bottom-most controls on the Open Timetable Data File dialog;

That would be the Test Sit-Times and the Deadhead Closure check boxes correct? Or is it the radio boxes where I can select fewest FPs, Balanced, Balanced Return Priority? Can I provide a screen cap of my settings?

• some identification of specific leg that is missing or that is overlapped - origin, destination, time, day of week (The data you were using last week creates over 160 flight plans with an average of 30 legs each. (I'm not about to check nearly 20,000 legs looking for a problem you have already identified.)

I have multiple instances of this problem? Do you want me to provide all instances or just a sampling? Also how are you getting 160 FPs when I am getting 78? You were running fewest FPs setting correct?

Hopefully you can answer these questions so I know exactly what information to give you.


I have also ran into an bug that might be related but I am not sure it concerns the A321 side of my time table data when I ran it in Balanced Mode and Balanced Return Priority Mode. it gave the following error: "
Unable to assign one or more legs for aircraft type "321"" and it had multiple missing and wrong Legs from my time table data of just the 321 and the full time table. The a321 only has 8 daily FPs so the bug should be easy to spot in this part. What info do you need to solve that on top of what you requested above? Do I need to start a new thread on this part to reduce confusion?

 

[gadgets]

Do you also want the Time Table data also or just the flight plan file set or traffic file?

I assume you are using the same data as before. If not, please also send the timetable data.

That would be the Test Sit-Times and the Deadhead Closure check boxes correct? Or is it the radio boxes where I can select fewest FPs, Balanced, Balanced Return Priority? Can I provide a screen cap of my settings?

A screenshot is fine. I just need to know what settings were used to generate the file set/traffic file you send

I have multiple instances of this problem? Do you want me to provide all instances or just a sampling?

One is fine, two or three are better (in case there's more than one cause.)

Also how are you getting 160 FPs when I am getting 78? You were running fewest FPs setting correct?

No, I was using balanced. But, it doesn't matter. Presumably a similar number of legs are generated in each case. My math was a little off in the earlier post. There only about 3000 legs generated - but still far more than I want to check.

Unable to assign one or more legs for aircraft type "321"" and it had multiple missing and wrong Legs from my time table data of just the 321 and the full time table.

That's most likely an issue with the assigned aircraft. With that message, missing legs should not be a surprise. Lets not worry about that one for now.

Don