Information update:: Ships Expected System Now Fully Upgraded
Posted by Forth & Clyde Control on 24-10-2025 13:04
The new ships expected system has been fully upgraded.
It operates in this way. My listener script when it sees a ship elsewhere with a home port, Clyde or Forth, in its resolved destination, sends a message to the database, this is picked up by my triage system
The ETA is first obtained from the ship, it defaults to that. If this is unclear, the system performs a distance calculation and presents either in my review page.
I then go to the port authority (Clyde only) and check with their scheduled movements. If theirs looks more stamped then theirs is used.
If none of the above looks right, or their is no authoritative source, I make a best estimated guess considering as many factors as possible.
Now that the system is fully refactored, it will let you know what method was used, so you too can be as fully informed and aware of the conditions.
I check often to ensure as close to accurate I can get, but clearly it's not always fail-safe and the Forth presents a problem in that official notice is lacking and ships to Forth's ports arrivals via ETA and calculations often mean not the port, but the anchorage arrival time...there is no way of knowing for sure. If do check as much as I can and if a ship goes to anchorage, I can only presume it to be an arrival state, otherwise I would have to keep entering guesses every day that ship is at anchor, but do not forget we have our live reports which never cease, so Forth watchers will always be aware of a ship status, simply by checking live reports to see if the ship came off the anchorage, or by looking at the logbook, which records all movements and the current day is available in the logbook as a summary of every live report past and current.
I hope this not only explains the systems here and how to get the best from them, but also assures you I am continuously refining the systems so that I have more time to tend them and make swift amendments where necessary.
It operates in this way. My listener script when it sees a ship elsewhere with a home port, Clyde or Forth, in its resolved destination, sends a message to the database, this is picked up by my triage system
The ETA is first obtained from the ship, it defaults to that. If this is unclear, the system performs a distance calculation and presents either in my review page.
I then go to the port authority (Clyde only) and check with their scheduled movements. If theirs looks more stamped then theirs is used.
If none of the above looks right, or their is no authoritative source, I make a best estimated guess considering as many factors as possible.
Now that the system is fully refactored, it will let you know what method was used, so you too can be as fully informed and aware of the conditions.
I check often to ensure as close to accurate I can get, but clearly it's not always fail-safe and the Forth presents a problem in that official notice is lacking and ships to Forth's ports arrivals via ETA and calculations often mean not the port, but the anchorage arrival time...there is no way of knowing for sure. If do check as much as I can and if a ship goes to anchorage, I can only presume it to be an arrival state, otherwise I would have to keep entering guesses every day that ship is at anchor, but do not forget we have our live reports which never cease, so Forth watchers will always be aware of a ship status, simply by checking live reports to see if the ship came off the anchorage, or by looking at the logbook, which records all movements and the current day is available in the logbook as a summary of every live report past and current.
I hope this not only explains the systems here and how to get the best from them, but also assures you I am continuously refining the systems so that I have more time to tend them and make swift amendments where necessary.