4 pointsby bekoeppel5 hours ago2 comments
  • btschaegg4 hours ago
    I tested the use case I could've really used this for, but it doesn't seem to be able to do this: "Biel to Zürich, but not through Grenchen".

    The SBB timetable app and website can become really unhelpful if there has been an "accident involving a person" [0]; other than that, I've got little issues with them day to day.

    But it seems your model doesn't have a way to know that the IC from Biel to Olten goes through Grenchen (it only presents the obvious routes that wouldn't work in this case).

    [0]: https://company.sbb.ch/en/railway-development/services-rus/r...

    • bekoeppel3 hours ago
      Oh I hadn't thought about that yet! But when there is a disruption like a accident or construction site, don't you get a re-route?
      • btschaeggan hour ago
        If it's something small, usually yes. But very often, that's still on the same routes (often, not all rails are blocked, so only some connections through the station suffer).

        But I've also seen my fair share of "trains in this direction won't recover for hours" over the years, and directly after such an incident, the official systems usually don't really adapt all that well. I don't know if they're "massaged" manually after that or if it's just a case of the entire system finally figuring out that an entire station is FUBARed, not only one or two scheduled connections…

  • vintagedave5 hours ago
    Nice. I tested a very simple example and got exactly what I hoped. Is there a LLM behind it or some more traditional kind of AI?
    • bekoeppel5 hours ago
      I built a combination of rules (e.g. HB is translated to Zurich HB) and LLM (Haiku). The rules were necessary because if I send a user to SBB.ch with destination "HB", SBB translates that to Herzogenbuchsee... not what I had expected.