Elektrine lite

← Feed

@numeredevs@fosstodon.org

2026-07-22 10:46 UTC

@loke@functional.cafe @jwildeboer@social.wildeboer.net Well, I might be wrong, but assuming you used https://cdn.gea.esac.esa.int/?prefix=Gaia/gfpr/Solar_system/sso_source/ as source, then there's at least one gap in file SsoSource_00.csv line 2614 (data row 2537), where no data is available for the state vector of the body. It's of course up to you and your design, how you want to handle such situations, but personally I'd consider to use either an empty field or NaN to signal the problem. Those "silent errors" can result in problems hidden for a long time.

Replies (1)

  • @loke@functional.cafe 2026-07-22 13:08

    @numeredevs@fosstodon.org @jwildeboer@social.wildeboer.net that's true. The behaviour I described was caused by the specific method I chose to parse the data (manual splitting). I have to admit not reading the specification, which I presume would mention the existence of blank state vectors. The 'proper' way to parse this based on my assumptions would be to use a regex to break out the components and then parse them as numbers. The regex match would then fail on an invalid string. This is actually what I usually do, but the manual solution showed off more of the array manipulation primitives in Kap compared to a simple call to regex:match. reference.html#_regexmatch_match_string_against_regex (and now I realise that I should document those functions more than just listing their names).

    Open ##5136245