Release EDMC - BioScan

[CMDR Zashyn]

Here is the line in the journal file that is causing the problem:

{ "timestamp":"2024-02-14T23:34:48Z", "event":"FSSDiscoveryScan", "Progress":-nan(ind), "BodyCount":0, "NonBodyCount":0, "SystemName":"HIP 8758", "SystemAddress":147933055331 }

It looks like the 'progress' being -nan(ind) is the problem. I changed this line in the journal to set 'progress' to 1.000000 (as I saw in several other FSSDiscoveryScan entries) and now the journal processing completes with no errors.

I have no memory of what I might have done to cause this entry to be created.

The journal file name is Journal.2024-02-14T170812.01.log
The journal file itself has a date of 02/28/2024 16:32, because I just edited it...

Thanks for the info. Honestly that seems like a bug in the ED logs but I'll see what I can do to work around it. I don't believe that's even a valid JSON value.
Was there any kind of python error in the EDMC debug log you could paste here? At the very least I could try to add a try/catch for unexpected values.

 

[CMDR Zashyn]

Somehow I accidentally created a second reply.

 

[athulin]

I don't believe that's even a valid JSON value.

It isn't: only 'false' 'true' and 'null' are allowed literals. Numbers always have to be written out, at least as a sequences of digits. And section 6 of RFC8259 says "Numeric values that cannot be represented in the grammar below (such as Infinity and NaN) are not permitted."

Looks like FDev just pushes a NaN with sign bit and payload ('ind') onto their JSON stream, and it doesn't check that the value is a legitimate JSON value before writing it.

Recommendation: bug report it. Even if the likelihood to get a repetition is low, it might catch the eye of anyone looking for nan-related issues in the future.

 

[maryth]

>Was there any kind of python error in the EDMC debug log

Not that I remember seeing, and I wasn't smart enough to make a copy of that log - it has since been overwritten. Sorry about that.

 

[CMDR Zashyn]

I do have a discord up now for any of my EDMC plugins in case you have feedback, issues, or other reports and want slightly more immediate responses.

Join the EDMC ExploData Suite Support Discord Server!

Check out the EDMC ExploData Suite Support community on Discord - hang out with 2 other members and enjoy free voice and text chat.

discord.gg

I may also put some beta releases on there as sometimes it's hard / time consuming to test everything by myself.

 

[nemwar]

Did anyone get these plugins run on linux?
I would like to use it but can't get it to run... they are shown in EDMC but as broken plugins.

 

[CMDR Zashyn]

I run it on Linux regularly. Did you install the python requirements as specified in the install instructions? Feel free to join the Discord channel if you need help.

 

[CMDR Zashyn]

Not that I remember seeing, and I wasn't smart enough to make a copy of that log - it has since been overwritten. Sorry about that.

Just FYI on one of the recent updates I extended the ExploData to allow for three or so JSON parse failures before erroring out. I figure if you get more than 3 of these in a file there's a deeper issue going on, but we can safely skip one entry if needs be.

Maybe at some point I can attempt to skip only bad values so I can still get some data for events BioScan cares about.

 

[fusionreactor]

I notice in one of your files that gives the conditions where a species may thrive namely clypeus.py there are no planet surface temperatures. Is this because they can be found at any temperature or you have no data. If it is the latter I may be able to help.

 

[CMDR Zashyn]

I notice in one of your files that gives the conditions where a species may thrive namely clypeus.py there are no planet surface temperatures. Is this because they can be found at any temperature or you have no data. If it is the latter I may be able to help.

Hey, sorry for the long wait. I'm bad about checking this thread.

Those are for water atmospheres and as I recall the temperature range was basically just the same as the global temperature range for any water bio so it wasn't a useful metric. (It wouldn't differentiate it from any other water bio.)

Since every check potentially adds additional processing time I've tried to cull criteria that's not actually useful for eliminating options.

 

[fusionreactor]

Understand your reasoning, thanks for the reply.

 

[CMDR Zashyn]

Bumping OP to indicate we're on release 2.9.0. A number of updates have happened since the previous update here. Some of the more significant updates include:

• Now providing a EDMC Flatpak-compatible ExploData version
• Several fixes and prediction corrections
  • Better black hole handling for bio colors
  • Revamped sinuous tuber zone data
  • Better named nebula checks
  • And more...
• Additional overlay improvements
  • Intelligently hiding the display depending on your status (location, supercruise, ship, suit)
  • Ship whitelist, so BioScan only renders in your explo ships

 

[CMDR Zashyn]

BioScan 2.10.1​

Translation Support​

2.10.0 brings translation support to BioScan, using the same translation schema as core EDMC. Currently Spanish, French, and German are supported. Submissions welcome. (German translations likely have issues, sorry.)

Special thanks to Malt Drinker for help with the French translations.
7/4/2025 - Russian translations added as additional download. Thanks to Иван Сусанин. Put the 'ru.strings' file in the L10n directory inside the plugin files.

Overlay Radar​

There is now an optional radar display for the overlay. This draws a radar that contains active scan locations and any waypoints set for the current planet. You can configure the center point and size (radius) in the settings, as well as the maximum distance value. (Scans and waypoints exceeding this distance still draw at the edge of the radar.) There are linear and logarithmic scaling options.

The radar orients itself to your current facing direction. That is, the front of your ship, SRV, or helmet. You can also optionally display your ship location. Note that this requires certain events to pick up. If you start EDMC already landed, leaving or entering your ship should set the ship location.

With no active scan, all waypoints will display in white with the genus indicated by three letters (e.g.. Bacterium = BAC). Once you start a scan, other waypoints will dim to gray while the relevant waypoints will highlight green. The minimum sample distance will show on the radar in orange (assuming the radar distance is large enough) as well as any existing scan locations. Just like the heading display of yore, waypoints that are too near a scan location will be pruned. Completed species will no longer display.

Other Changes & Fixes​

• Added status flags introduced by ED 4.1.0.2 to avoid crashes in the Status.json parser
• Added option to shorten number displays. (e.g. 19,010,800 becomes 19.01m)
• Added line spacing configuration for overlay text displays
• Add planetary nebula "Shrogeau QO-R e4-711" to the list
• Add major silicate vapor volcanism to blatteum sinuous tuber criteria
• Add major rocky volcanism to viride sinuous tubers criteria
• Fixes for initialization if cmdr or ship name not present

NOTE​

edmcoverlay2 (with the X11 renderer) lacks proper support for vector markers, which are used heavily by the radar. Use the attached patched version to correct this issue. (You don't need this if you use Windows.) And you'll need to follow the install instructions from that repo.