Results 1 to 8 of 8

Thread: .tdb file - TrackNode Query

  1. #1
    Join Date
    May 2010
    Location
    Worksop, UK
    Posts
    2,523

    Default .tdb file - TrackNode Query

    Hi All,
    In entries such as this :
    TrackNode ( 23164 TrJunctionNode ( 0 39445 0 )
    UiD ( -6097 15006 25881 0 -6097 15006 290.152 91.4283 455.169 0 -2.88099 0 )
    TrPins ( 1 2
    TrPin ( 0 0 )
    TrPin ( 23165 1 )
    TrPin ( 23171 1 )
    what is the purpose of the TrPin ( 0 0 ) line?

    For each TrackNode with such an entry, Open Rails gives two warning messages :
    "Track node nnnnn pin 0 has invalid link to track node 0" and
    "Ignored invalid track node nnnnn pin [0,0] link to track node 0"

    My question is, can that entry be removed?
    if so, should the 'TrPins ( 1 2' line be changed to 'TrPins ( 1 1' and the '1' on the next TrPin line changed to '0'?
    Or could such changes be "fatal" to the route?

    Or, maybe, Open Rails shouldn't give the warnings if the entries are deemed to be 'harmless'?!

    This query was prompted by my running a route having 183 'TrPin ( 0 0 )' lines which created a total of 366 warnings in the OR log!

    Cheers,
    Ged
    Last edited by slipperman; 02-12-2022 at 12:17 PM.

  2. #2
    Join Date
    Jul 2013
    Location
    Mont-St-Hilaire, QC
    Posts
    274

    Default

    Hi Ged,

    I am not an expert, but it seems that the "(" do not match the ")". First line, you open one, and 3rd line you open another, but they are never closed.

    Michel

  3. #3
    Join Date
    May 2010
    Location
    Worksop, UK
    Posts
    2,523

    Default

    Hi Michel,
    Thanks for replying, but it's nothing to do with matched/unmatched brackets! It's my fault for missing them from the quote - when used in a quote they appear as emoticons!!

    I'm not saying the entry doesn't work, because it does, just asking a question (or two)

    Cheers,
    Ged

  4. #4
    Join Date
    Nov 1999
    Location
    Chippenham, Wiltshire, UK.
    Posts
    6,978

    Default

    TrPin ( 0 0 ) is a rogue blue pole, a track node not linked to another node. UKTS_22427 is a TDB primer and does give a method for removing these errors, but it involves use of the route editor and a text editor to change each bad trpin entry in the TDB.

    As these rogue poles do not seem to affect the running of a route, perhaps we should be asking the OR dev team to suppress these messages.
    Beer is not a matter of life or death, it is much more serious than that.

  5. #5

    Default

    What harm is caused by the warnings? They're a legitimate error, and being reported as such. It shouldn't cause any problems running the route.

  6. #6
    Join Date
    Feb 2013
    Location
    known universe
    Posts
    2,727

    Default

    Quote Originally Posted by eolesen View Post
    What harm is caused by the warnings? They're a legitimate error, and being reported as such. It shouldn't cause any problems running the route.
    It's all about the amount of errors reported in the log...combing through the stuff a user cannot correct to find some useful information about errors/warnings they can correct...there have been some discussions about how to mitigate all the warnings in the logs. It's especially difficult for new OR users unaccustomed to using the log to diagnose problems.

    Currently there are options to -- show/not show -- verbose eng-wag configuration messages and shape warnings...why not add other options...this appears a likely candidate. Perhaps another Options tab devoted to what warnings a user wants to appear in log? -- or just add that user selection to the "Data logger" tab.
    Last edited by R. Steele; 02-12-2022 at 05:02 PM.
    Cheers, Gerry
    It's my railroad and I'll do what I want! Historically accurate attitude of US Railroad Barons.
    Forever, ridin' drag in railroad knowledge.


  7. #7
    Join Date
    Sep 2006
    Location
    .
    Posts
    2,848

    Default

    Quote Originally Posted by baldwin View Post
    As these rogue poles do not seem to affect the running of a route

    I wouldn't make an assumption that broad.

    If a route has that many rogue blue poles, then perhaps the issue is with the route itself. If it runs fine in OR with errors logged, that's alright, too.

    I would rather have a logged indicator that something might not be right with the route when it comes to debugging other activity aspects that are not performing as expected.

    Lastly, doesn't TSRE have some feature to auto-fix blue poles?

  8. #8
    Join Date
    May 2010
    Location
    Worksop, UK
    Posts
    2,523

    Default

    Hi Chaps,
    @baldwin : Many thanks for that information, especially the TDB_Primer.

    @eolesen : They don't cause any harm, except by bulking out the log file, by more than 360 lines in the case of the route I ran.

    Cheers,
    Ged

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •