MattG's Observatory plugins
- Thread starter MattG
- Start date
Have a problem can't seem to shift, tried uninstalling, reinstalling but my friends use it just fine! Can anybody help with this error plz?
'1 error encountered.
Error in Observatory Botanist while handling ScanOrganic: Value cannot be null. (Parameter 'key')
Full error details logged to ObservatoryErrorLog file in your documents folder.'
Douments folder:[08/04/2023 09:31:26]:
Error in Observatory Botanist while handling ScanOrganic: Value cannot be null. (Parameter 'key') - { "timestamp":"2023-01-24T10:27:29Z", "event":"ScanOrganic", "ScanType":"Analyse", "SystemAddress":0, "Body":0 }
Thanks
'1 error encountered.
Error in Observatory Botanist while handling ScanOrganic: Value cannot be null. (Parameter 'key')
Full error details logged to ObservatoryErrorLog file in your documents folder.'
Douments folder:[08/04/2023 09:31:26]:
Error in Observatory Botanist while handling ScanOrganic: Value cannot be null. (Parameter 'key') - { "timestamp":"2023-01-24T10:27:29Z", "event":"ScanOrganic", "ScanType":"Analyse", "SystemAddress":0, "Body":0 }
Thanks
Last edited:
Observatory Core v 0.2.23060.2034
BioInsights v0.23.93.957
TTS Voice: Ivona 2 Amy OEM
Forgive me if this is a known, as I've just started using this brilliant program and plugin:
Every time the TTS engine finishes a notification, it says 'dot'. I'm assuming that there's a space in the string being passed to it between the end of the notification and a full stop, so it's treating it as separate.
Is this a known issue?
Cheers!
BioInsights v0.23.93.957
TTS Voice: Ivona 2 Amy OEM
Forgive me if this is a known, as I've just started using this brilliant program and plugin:
Every time the TTS engine finishes a notification, it says 'dot'. I'm assuming that there's a space in the string being passed to it between the end of the notification and a full stop, so it's treating it as separate.
Is this a known issue?
Cheers!
Wasn't aware of this, I'll see if I can track down and eliminate the rogue full stop.
In the interim you could give the Herald plugin a try, I don't think that is affected by this - I use Herald and haven't encountered the problem. Herald also sounds a lot nicer than the TTS voices.
I use a cereproc voice (https://www.cereproc.com/en) which are expensive but very good. I don't have the problem mentioned by Moirai but mine does use a hard, short A instead of a soft A when is says, for instance, 'body 1 A'. I think I can probably fix this by fiddling with a file where you can define/override pronunciations but I've never got around to it.
Just an update: I notice that the notification for reaching minimum distance from the previous sample doesn't have the 'dot' addition. Maybe that has no full stop at the end...
I'll give it a spin, although I prefer to limit the number of different voices I'm using in Elite (currently Celeste HCS voice pack and Ivona Amy for EDDI). Another different voice may get a bit too much.
That said, the 'dot' isn't any annoyance or anything; just a curiosity.
Appreciate the reply.
Just an update: I notice that the notification for reaching minimum distance from the previous sample doesn't have the 'dot' addition. Maybe that has no full stop at the end...
I'll give it a spin, although I prefer to limit the number of different voices I'm using in Elite (currently Celeste HCS voice pack and Ivona Amy for EDDI). Another different voice may get a bit too much.
That said, the 'dot' isn't any annoyance or anything; just a curiosity.
Appreciate the reply.
Yep that's fair enough, I expect it's an easy enough fix.
@Kerada I need to tweak the way bodies are read out. It's on my list, just never seem to get round to it
This is a kind of indirect question regarding BioInsight ...
Does the development of this plugin depend on information collected by some tool, or some plugin? That is, would the use of such tool or plugin lead to improvements in classification?
(I'm imagining there's some kind of classification engine in there, relying on some kind of training data, to which improvements / added coverage may be desirable. )
Does the development of this plugin depend on information collected by some tool, or some plugin? That is, would the use of such tool or plugin lead to improvements in classification?
(I'm imagining there's some kind of classification engine in there, relying on some kind of training data, to which improvements / added coverage may be desirable. )
BioInsights itself used to record certain information when it encountered things it hadn't predicted. I disabled it a whole back but eventually I plan to re-implement it. There's a few things I want to sort before that though (submission can also be disabled in settings too).
At the moment, the biggest source of updated data comes from users who contact me when they encounter an unexpected bio - usually a screenshot of BI and data submitted to EDSM/EDDN is enough to deduce what is wrong in rules. Sometimes still check Cannon's bio data too (though I think it's currently not being updated).
So I guess the answer is: use BioInsights and let me know of issues, ensure data being submitted to EDDN / EDMC, and can't hurt to run Cannon's EDMC plugin too (plus it's super useful for a whole bunch of other things too).
Yep, this is on my to-do list. I was half waiting for Vith to finish the Core UI rewrite but I might get to it a bit sooner.Would it be possible to add an option to only show entries for the current system in the Evaluator plugin? Must admit that I'm finding, with FSS scans of each system I pass through, it tends to get a bit crowded with data from multiple systems.
If not, no probs.
Just received my first "NOT PREDICTED" bio. I was surprised that the planet entry itself didn't even show up on the list until I went down to scan it. I just happened to notice that it had a 'high value' target.
Not sure if you need the journal entry itself.
Please let me know if you require other information.
And thank you again for this utility, even though it is probably going to take me 10x longer to get to Beagle Point.
Not sure if you need the journal entry itself.
Code:
{ "timestamp":"2023-05-09T21:53:28Z", "event":"SAAScanComplete", "BodyName":"Blu Brou RV-N b20-0 A 1", "SystemAddress":818057280689, "BodyID":3, "ProbesUsed":4, "EfficiencyTarget":6 }
{ "timestamp":"2023-05-09T21:53:28Z", "event":"SAASignalsFound", "BodyName":"Blu Brou RV-N b20-0 A 1", "SystemAddress":818057280689, "BodyID":3, "Signals":[ { "Type":"$SAA_SignalType_Biological;", "Type_Localised":"Biological", "Count":1 } ], "Genuses":[ { "Genus":"$Codex_Ent_Stratum_Genus_Name;", "Genus_Localised":"Stratum" } ] }
{ "timestamp":"2023-05-09T21:53:29Z", "event":"Scan", "ScanType":"Detailed", "BodyName":"Blu Brou RV-N b20-0 A 1", "BodyID":3, "Parents":[ {"Star":1}, {"Null":0} ], "StarSystem":"Blu Brou RV-N b20-0", "SystemAddress":818057280689, "DistanceFromArrivalLS":297.406595, "TidalLock":false, "TerraformState":"", "PlanetClass":"High metal content body", "Atmosphere":"thin argon rich atmosphere", "AtmosphereType":"ArgonRich", "AtmosphereComposition":[ { "Name":"Oxygen", "Percent":56.207317 }, { "Name":"Argon", "Percent":35.776932 }, { "Name":"CarbonDioxide", "Percent":7.850077 } ], "Volcanism":"", "MassEM":0.140871, "Radius":3376258.750000, "SurfaceGravity":4.925595, "SurfaceTemperature":171.691681, "SurfacePressure":5845.939453, "Landable":true, "Materials":[ { "Name":"iron", "Percent":21.992401 }, { "Name":"nickel", "Percent":16.634132 }, { "Name":"sulphur", "Percent":16.622898 }, { "Name":"carbon", "Percent":13.978137 }, { "Name":"chromium", "Percent":9.890714 }, { "Name":"phosphorus", "Percent":8.949043 }, { "Name":"vanadium", "Percent":5.400568 }, { "Name":"selenium", "Percent":2.601624 }, { "Name":"cadmium", "Percent":1.707810 }, { "Name":"molybdenum", "Percent":1.436091 }, { "Name":"technetium", "Percent":0.786579 } ], "Composition":{ "Ice":0.041774, "Rock":0.640321, "Metal":0.317905 }, "SemiMajorAxis":89074948430.061340, "Eccentricity":0.001909, "OrbitalInclination":-0.568850, "Periapsis":227.498254, "OrbitalPeriod":22321251.034737, "AscendingNode":110.091240, "MeanAnomaly":120.022181, "RotationPeriod":99476.889888, "AxialTilt":0.050283, "WasDiscovered":false, "WasMapped":false }Please let me know if you require other information.
And thank you again for this utility, even though it is probably going to take me 10x longer to get to Beagle Point.
Well, these things are defined by their parent star, so the parent star type is needed.
No problem though, the system is on EDSM, so Matt can look it up (it's an M class).
Didn't show up? That suggests you visited the planet not because BioInsight directed you to it, but because the scan showed there was a Bio feature -- is that right?
Is that intended, or is it a bug?
I'm trying to get my head around BioInsight SOP. If it doesn't show all bio signals discovered, even if a prediction about what is there cannot be made, the player must double check the results of the DSS scan against BioInsight output to identify any discrepancies, and then also go for those to verify what is there.
If the star type isn't detected on arrival, that is if you have maybe visited the system previously, the autoscan and honk won't report the star type through the journal, because you already know what's there, and then any bio based on the star type can't be predicted by bio-insights, I have had this happen to me a couple of times. But the FSS will of course still show the number of bio signals on the body and this won't match the number in bio-insights. Basically bio-insights can't even make a guess at what might be there. When you DSS the planet it will of course then know what's there due to the bio types being reported to the journal, but it can't determine why they are there because it still doesn't know the star type, so you have an unexpected bio message in bio-insights.
Thanks for this, and especially providing journal entries. As others have noted, in some cases I also need details on star types but in this instance it's because of the atmosphere type not being one of the expected ones - don't recall seeing Tectonicas on an Argon-Rich body before. I'll get it fixed in criteria, but it might be a short while before new version is out - I'm still waiting for Vith to finish UI rewrite and that's going to require a chunk more updating to plugins.
Yeah I had a look at the system in EDSM and it has only had 2 visitors, obviously the original discoverer and one more, but it's good to know there's still new data out there to find at least, I usually find argon rich gives me bacteria mostly, very rare to find other stuff, but at least our reports are helping get the plugins updated.