Jump to content




Help Support AmtrakTrains.com by donating using the link above or becoming a Supporting Member.

Photo

ASMAD update - improvements to connecting trains search


  • Please log in to reply
24 replies to this topic

#1 acelafan

acelafan

    Conductor

  • Members
  • PipPipPipPipPip
  • 854 posts
  • Gender:Male
  • Location:Atlanta, GA

Posted 09 August 2015 - 05:49 PM

All,

 

I finally got a chance to update the connecting trains search on ASMAD.  Now it will automatically list missed connections in red where the arrival information is known.  Sometimes only departure data is known for the first train, and in those cases likely missed connections are displayed in orange

 

I also include the count and percentage of missed trains at the bottom of the table, like this:

 

20150809_6_50_CHI_connections.png

 

(Link)

 

JB started gathering additional info in the Amtrak Status Maps beginning in late May for this improvement.  (Some missed connections may not be automatically flagged before then.)

 

It was a good suggestion by a few people.

 

CJ


ASMAD - Has your train been running on time?

 

Amtrak Timetable Archives - PDFs since 2009


#2 Bob Dylan

Bob Dylan

    Engineer

  • Members
  • PipPipPipPipPipPip
  • 16,828 posts
  • Gender:Male
  • Location:Austin Texas
  • Interests:Passenger Trains/Travel/Sports/Gov't/ Politics/History/Reading/
    Movies/Music/Space-Ancient Aliens

Posted 09 August 2015 - 05:56 PM

You guys do a fantastic job! Thanks for sharing!😉
"There's Something About a Train! It's Magic!"-- 1970s Amtrak Ad
 "..My heart is warm with the friends I make,and better friends I'll not be knowing,
Yet there isn't a train I wouldn't take,No matter where its going!.." -Edna St. Vincent Millay

#3 willem

willem

    Conductor

  • Members
  • PipPipPipPipPip
  • 906 posts
  • Gender:Male

Posted 09 August 2015 - 06:09 PM

Yes, thank you.

#4 Rail Freak

Rail Freak

    Engineer

  • Members
  • PipPipPipPipPipPip
  • 4,584 posts
  • Gender:Male
  • Location:Tampa Bay, Florida
  • Interests:Experiencing the country by RAIL!!!
    U.S. & Native American History

Posted 09 August 2015 - 06:16 PM

WOW, Thanx!!!


A Rookie No More! But Still A Lot Of Track To Travel !!!
Silver Meteor #97(6) & #98 (4), Silver Star #91 (2), Capitol Limited #29 & #30(6), Empire Builder #7,#8,#27(2) &#28(4) Coast Starlight #11 (6) & #14(5), California Zephyr #5 (2) & #6 (5), Cascades #506, City of New Orleans #58, #59 (2), South West Chief #3 (4), Lake Shore Limited #49, Maple Leaf #63, San Joaquin #714, Pacific Surfliner #774, Texas Eagle #422 (2), Cardinal #50, Crescent #19, Sunset Limited #1. Approx. 60,169 miles & 41 states!

 


#5 FrensicPic

FrensicPic

    Engineer

  • Members
  • PipPipPipPipPipPip
  • 2,353 posts
  • Gender:Male
  • Location:LAX
  • Interests:Trains, photography and radio communications...not necessarily in that order.

Posted 10 August 2015 - 04:10 AM

Now I don't have to do my own math! Nice improvement...thanks.

John...

29,076 miles on the Coast Starlight, Sunset Limited, Texas Eagle, Southwest Chief, Empire Builder, California Zephyr and Capitol Limited.

5540 miles booked for this fall on the Sunset Limited, City of New Orleans, Illini/Saluki, Southwest Chief.

More miles on the Pacific Surfliner, Metrolink, White Pass and Yukon Route, Grand Canyon Railway, Napa Valley Wine Train, Fillmore and Western and private railcars with LARail.com

Photos: http://www.flickr.co...rensicpic/sets/<p> 


#6 Anderson

Anderson

    Engineer

  • Members
  • PipPipPipPipPipPip
  • 8,463 posts
  • Gender:Male
  • Location:Virginia

Posted 10 August 2015 - 05:34 AM

Very nice...and very interesting, being able to run checks on various same-day round-trips (e.g. RVR-WAS-RVR in a single day...for example, the NB Star has only misconnected with the SB Meteor twice this summer).


Capitol Limited (7), CA Zephyr (4) Lake Shore Limited (1), Acela (2), NE Regional (2), Sliver Meteor (4)

Upcoming: Silver Meteor (1), Lake Shore Limited (1), SW Chief (2), MO River Runner (1), Texas Eagle (1)

Possibly Upcoming: Either Texas Eagle (1), Capitol Limited (1), Silver Meteor (2) or Texas Eagle (1), Capitol Limited (1), Silver Meteor (1)

#7 Ryan

Ryan

    Engineer

  • Members
  • PipPipPipPipPipPip
  • 16,036 posts
  • Gender:Male
  • Location:OTN
  • Interests:a fact checker combined with a ferret

Posted 10 August 2015 - 08:31 AM

This is an awesome resource, keep up the great work.
Posted Image

Disclaimer: Any images or links you see in my post may in fact be invasive advertising or even fraudulent phishing attacks silently injected into my post by our spam based hosting service. If anything looks suspicious or inappropriate or you have any doubt whatsoever then do not click any links (particularly those appearing in green and/or with a double underline) or interact with the spam in any way. You may also want to consider using ad-blocking plugins such as Adblock Plus and/or Ghostery)to help reduce the number and severity of advertising scams directed at you.

#8 George K

George K

    Engineer

  • Members
  • PipPipPipPipPipPip
  • 1,112 posts
  • Gender:Male
  • Location:The Chicago Burbs
  • Interests:Ask me!

Posted 10 August 2015 - 12:36 PM

Fantastic. Thank you.


4/1/1955 - NYC "Pacemaker" - NYP to CHI; 9/14 - EB - CHI to PDX , CS - PDX to EMY, CZ - EMY to CHI; 3/15 CONO - Round trip; 9/15 CL CHI to WAS, Acela WAS to BOS, LSL BOS to CHI; 11/15 CONO - Round trip; 5/16 EB - Round trip; 12/16 CONO -  Round Trip; 5/17 EB - Round trip; 10/17 CONO - Round trip

#9 Anderson

Anderson

    Engineer

  • Members
  • PipPipPipPipPipPip
  • 8,463 posts
  • Gender:Male
  • Location:Virginia

Posted 11 August 2015 - 03:16 AM

Something I've noticed..."likely missed connections" doesn't actually appear even when you have the inbound train arriving at the same time as the outbound train is leaving.  30 seconds may be an acceptable connection time in Germany, but just try that in New York...


Capitol Limited (7), CA Zephyr (4) Lake Shore Limited (1), Acela (2), NE Regional (2), Sliver Meteor (4)

Upcoming: Silver Meteor (1), Lake Shore Limited (1), SW Chief (2), MO River Runner (1), Texas Eagle (1)

Possibly Upcoming: Either Texas Eagle (1), Capitol Limited (1), Silver Meteor (2) or Texas Eagle (1), Capitol Limited (1), Silver Meteor (1)

#10 acelafan

acelafan

    Conductor

  • Members
  • PipPipPipPipPip
  • 854 posts
  • Gender:Male
  • Location:Atlanta, GA

Posted 11 August 2015 - 09:35 PM

Something I've noticed..."likely missed connections" doesn't actually appear even when you have the inbound train arriving at the same time as the outbound train is leaving.  30 seconds may be an acceptable connection time in Germany, but just try that in New York...

Good eye!  Fixed.  I also fixed a bug where a train arriving exactly on time was getting flagged incorrectly. 

 

Glad to hear the page is useful.


ASMAD - Has your train been running on time?

 

Amtrak Timetable Archives - PDFs since 2009


#11 Thirdrail7

Thirdrail7

    Engineer

  • Members
  • PipPipPipPipPipPip
  • 2,773 posts

Posted 11 August 2015 - 09:46 PM

I usually stay out of these sort of threads, but I do have some questions. There are times that connecting trains aren't held if there are no connecting passengers (which happens.) How do you account for that? Additionally, there are times when known connections are going to be missed and passengers are often bussed, cabbed etc to intercept their connections at other stations.  Your chart doesn't seem to show that so is this just a "pure" train to train connection you're logging or is this passenger misconnections?

 

While we're at it, does your status page update itself in real time as corrections are made? I bring this up because recently an initial terminal decided to flip flop the consists for two trains without telling anyone. As such, the first train out had the second trains consist and the second train had the first consist.

 

As the first train traveled up the line, it OSd everything an hour early for the arrival and on time for the departure. These are the times that are picked up by your train trackers. When the second train utilizing the first consist departed, every arrival time on the first train was overridden and showed an hour late.

 

It was fixed hours later. Would the adjustment show?


Edited by Thirdrail7, 11 August 2015 - 09:54 PM.

They say laughter is the best medicine. Obviously they never posted on AU.


#12 acelafan

acelafan

    Conductor

  • Members
  • PipPipPipPipPip
  • 854 posts
  • Gender:Male
  • Location:Atlanta, GA

Posted 11 August 2015 - 09:54 PM

I usually stay out of these sort of threads, but I do have some questions. There are times that connecting trains aren't held if there are no connecting passengers (which happens.) How do you account for that? Additionally, there are times when known connections are going to be missed and passengers are often bussed, cabbed etc to intercept their connections at other stations.  Your chart doesn't seem to show that so is this just a "pure" train to train connection you're logging or is this passenger misconnections?

Yes to your last question - this is just pure train-to-train connection history information.  I have no way of knowing if Amtrak got the through passengers (if any) to their final destination via alternate means in the event of a missed connection.  It's a valid point.


ASMAD - Has your train been running on time?

 

Amtrak Timetable Archives - PDFs since 2009


#13 John Bobinyec

John Bobinyec

    Engineer

  • Members
  • PipPipPipPipPipPip
  • 1,493 posts
  • Gender:Male
  • Location:CYN

Posted 12 August 2015 - 05:00 AM

 

While we're at it, does your status page update itself in real time as corrections are made? I bring this up because recently an initial terminal decided to flip flop the consists for two trains without telling anyone. As such, the first train out had the second trains consist and the second train had the first consist.

 

As the first train traveled up the line, it OSd everything an hour early for the arrival and on time for the departure. These are the times that are picked up by your train trackers. When the second train utilizing the first consist departed, every arrival time on the first train was overridden and showed an hour late.

 

It was fixed hours later. Would the adjustment show?

ASMAD gets its data from Amtrak Status Maps (ASM) once per day.  ASM gets its data from Amtrak as a train progresses with its trip.  Once the times are recorded by ASM there is no automatic way for it to go back and adjust times that Amtrak has subsequently changed.  However, if someone brings the situation to my attention, I can have ASM re-record the times - if it's not too late.  Amtrak only keeps about 5 days worth of data on-line.  If the times are re-recorded, ASMAD will get the new times when it next gathers data from ASM.

 

jb

Amtrak Status Maps


LDS Been On:

 

Old: Phoebe Snow (EL), Montrealer (AT), Laurentian (D&H)

RBBB: St. Petersburg - W. Palm Beach, Lakeland - Atlanta, Baltimore - NYC, Rochester, NY - Hartford, Albuquerque - Salt Lake City, Denver - Chicago

Modern: Ocean (VIA), Silver Star, Capitol Limited, Texas Eagle, Autotrain, Carolinian, Southwest Chief, California Zephyr, Lake Shore Limited

 


#14 willem

willem

    Conductor

  • Members
  • PipPipPipPipPip
  • 906 posts
  • Gender:Male

Posted 12 August 2015 - 10:53 AM

John, thanks for doing the tedious, hands-on work, like forcing a collection of data after the fact. I appreciate the work that went into ASM, and I'm grateful that you are so responsive to comments.

#15 Thirdrail7

Thirdrail7

    Engineer

  • Members
  • PipPipPipPipPipPip
  • 2,773 posts

Posted 13 August 2015 - 03:08 PM

I have one more scenario for you if you don't mind. Let's say the notorious 94 is up to its usual tricks and is late operating on the RF&P sub. Amtrak decides to run an on time section of 94 at WAS. Once 94 arrives WAS, it assumes the slot and identity of  train 178 to BOS. The Amtrak Status map would show both 94 and 178 as operating on time WAS-BOS, but the actual passengers for late 94 would be entered in the remarks section to show their true arrival times.

 

I suspect something like that wouldn't show up on your  page?


They say laughter is the best medicine. Obviously they never posted on AU.


#16 acelafan

acelafan

    Conductor

  • Members
  • PipPipPipPipPip
  • 854 posts
  • Gender:Male
  • Location:Atlanta, GA

Posted 13 August 2015 - 04:18 PM

I have one more scenario for you if you don't mind. Let's say the notorious 94 is up to its usual tricks and is late operating on the RF&P sub. Amtrak decides to run an on time section of 94 at WAS. Once 94 arrives WAS, it assumes the slot and identity of  train 178 to BOS. The Amtrak Status map would show both 94 and 178 as operating on time WAS-BOS, but the actual passengers for late 94 would be entered in the remarks section to show their true arrival times.

 

I suspect something like that wouldn't show up on your  page?

If Amtrak switches a particular consist to a new identity/number, I believe they re-program the onboard GPS device to that new number.  ARROW should then report the AR/DP times for the train that the GPS device is programmed for.  That would show up in the ASM files.


ASMAD - Has your train been running on time?

 

Amtrak Timetable Archives - PDFs since 2009


#17 Ryan

Ryan

    Engineer

  • Members
  • PipPipPipPipPipPip
  • 16,036 posts
  • Gender:Male
  • Location:OTN
  • Interests:a fact checker combined with a ferret

Posted 13 August 2015 - 06:16 PM

I think that is his point. Say I board 94 in Richmond. We arrive in Washington late. Meanwhile, Amtrak runs an on-time section of 94 leaving WAS on time, and arriving at NYP on time.

Meanwhile, 94 becomes 178 in WAS and also runs on time to NYP.

Our hypothetical traveler from Richmond gets off in New York later than planned, but that isn't reflected in the database since both trains are "on time".

With some data analysis, you could find it, look for a 94 that departs WAS before it arrives in ALX. :D
Posted Image

Disclaimer: Any images or links you see in my post may in fact be invasive advertising or even fraudulent phishing attacks silently injected into my post by our spam based hosting service. If anything looks suspicious or inappropriate or you have any doubt whatsoever then do not click any links (particularly those appearing in green and/or with a double underline) or interact with the spam in any way. You may also want to consider using ad-blocking plugins such as Adblock Plus and/or Ghostery)to help reduce the number and severity of advertising scams directed at you.

#18 acelafan

acelafan

    Conductor

  • Members
  • PipPipPipPipPip
  • 854 posts
  • Gender:Male
  • Location:Atlanta, GA

Posted 13 August 2015 - 08:08 PM

With some data analysis, you could find it, look for a 94 that departs WAS before it arrives in ALX. :D

Ah, yes that's possible, maybe on a rainy day.   ;) 

 

Also, a note may appear at the top of the status maps file if John knows it's a split train.  In fact, this happened for Train #79 originating July 22 but my code doesn't look for that.


ASMAD - Has your train been running on time?

 

Amtrak Timetable Archives - PDFs since 2009


#19 acelafan

acelafan

    Conductor

  • Members
  • PipPipPipPipPip
  • 854 posts
  • Gender:Male
  • Location:Atlanta, GA

Posted 13 August 2015 - 09:34 PM

I had to look. 

 

Two good examples of #94 departing WAS before departing ALX are 03/03/2014 and 08/20/2014.

 

In the first case the train was 7+ hours late at ALX; in the second it was 3+ hours late. 

But they both got to BOS less than 30 minutes late.   :giggle:  

 


ASMAD - Has your train been running on time?

 

Amtrak Timetable Archives - PDFs since 2009


#20 John Bobinyec

John Bobinyec

    Engineer

  • Members
  • PipPipPipPipPipPip
  • 1,493 posts
  • Gender:Male
  • Location:CYN

Posted 14 August 2015 - 04:19 AM

By the way, when they start out an extra train set to cover the regular train schedule of a late train, we get the following four scenarios because of the way Amtrak Status Maps (ASM) works.  In order to keep the network traffic to a minimum, ASM only looks for a train at a station when it's possible.  For example, on the 3/3/2014 version of 94 in the last post, being 7H 49M late in ALX, it wouldn't even start looking for the train in WAS until 9.24 p.m. (regular arrival time 1.35 p.m.) because it thinks that 94 couldn't possibly get to Washington before that.  This leads to four scenarios:

 

A)  Amtrak identifies the extra train as the original train, and unidentifies the late train when it gets to the origin station for the extra train. On the maps this will show original 94 up through WAS and then stalled until new-94's time gets late enough for ASM to start looking for it again.  Then suddenly it will jump way up the line.

 

B) Amtrak does not identify the extra train as the original train.  In this case the new train will be invisible and never appear on the maps at all.

 

C) Amtrak identifies BOTH trains as the original train.  In this case the maps will show the progress of the original train.  The extra train will be invisible.

 

D) Amtrak unidentifies BOTH trains.  In this case the extra train will be invisible and the original train will seem to stall.

 

That's enough of these thought experiments.  I've got to get ready to go to work.

 

jb


Edited by John Bobinyec, 14 August 2015 - 01:28 PM.

LDS Been On:

 

Old: Phoebe Snow (EL), Montrealer (AT), Laurentian (D&H)

RBBB: St. Petersburg - W. Palm Beach, Lakeland - Atlanta, Baltimore - NYC, Rochester, NY - Hartford, Albuquerque - Salt Lake City, Denver - Chicago

Modern: Ocean (VIA), Silver Star, Capitol Limited, Texas Eagle, Autotrain, Carolinian, Southwest Chief, California Zephyr, Lake Shore Limited

 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users