Its in the Botanist plugin so not in the same place. BioInsight is so much better than Botanist. I'd rather not have to flick between the two.
MattG's Observatory plugins
- Thread starter MattG
- Start date
A couple of updates:
BioInsights now has a field to show if analysing a Bio is complete or not. This should help you work out what you were doing when you last played. It should also clear the display when only showing current system upon jumping to the system rather than waiting until it finds an interesting Scan to process. It should also be a bit cleverer about if we're playing in Odyssey or not - so shouldn't require starting Observatory before the game.
BoxelStats now has an option to only show averages based on complete systems. This is disabled by default. This has caused a structure change in the data stored, so you will need to do a "Read All" to restore the data (just once). The Visited column now has another number in brackets to show the number of completed systems. One more point with the "Only report stats for completed systems" option - lets say you visit 300 systems but only fully scan 100. You see 10 ELWs, but only 4 in fully scanned systems. The ELW Count will show 10, but the average should show 1 in 25 because it will only count the ELWs in fully scanned systems against the number of fully scanned systems. I thought about making it show 4 in the ELW count, but this would be even more misleading I think. I also toyed with showing both numbers, but then it starts to look like information overload.
I currently have exetremely limited play time so have not been able to test as much as I would like - accordingly, please let me know if things don't (or do!) work as expected.
BioInsights now has a field to show if analysing a Bio is complete or not. This should help you work out what you were doing when you last played. It should also clear the display when only showing current system upon jumping to the system rather than waiting until it finds an interesting Scan to process. It should also be a bit cleverer about if we're playing in Odyssey or not - so shouldn't require starting Observatory before the game.
BoxelStats now has an option to only show averages based on complete systems. This is disabled by default. This has caused a structure change in the data stored, so you will need to do a "Read All" to restore the data (just once). The Visited column now has another number in brackets to show the number of completed systems. One more point with the "Only report stats for completed systems" option - lets say you visit 300 systems but only fully scan 100. You see 10 ELWs, but only 4 in fully scanned systems. The ELW Count will show 10, but the average should show 1 in 25 because it will only count the ELWs in fully scanned systems against the number of fully scanned systems. I thought about making it show 4 in the ELW count, but this would be even more misleading I think. I also toyed with showing both numbers, but then it starts to look like information overload.
I currently have exetremely limited play time so have not been able to test as much as I would like - accordingly, please let me know if things don't (or do!) work as expected.
Thank you for such a swift turn around on those requests for changes to BioInsights. I will give it a go tonight and let you know how I get on.
I don't use BoxelsStats. Not even sure what it is. So I will leave that for someone else to look at.
I don't use BoxelsStats. Not even sure what it is. So I will leave that for someone else to look at.
Clearing list on jumping to new system - Works!
Filling in "Seen" column - Filled in if scanned using SRV or hand scanner - Works!
Filling in "Analysis" column - Does not update on an analysis, but does on the next SRV scan. "In progress" displayed, but again, only after a SRV scan.
Filling in "Seen" column - Filled in if scanned using SRV or hand scanner - Works!
Filling in "Analysis" column - Does not update on an analysis, but does on the next SRV scan. "In progress" displayed, but again, only after a SRV scan.
Ooh nice, I will test it for you!
Regarding the BoxelStats option, this is how it looks like.
All visited systems count:
Only the fully FSS scanned systems count:
Interesting are the columns regarding ELWs, AWs, tWWs, tHMCs. As I always fully scan the ELW systems, that result is correct in the all visited view, but skewed in the fully scanned statistic, while for the others the fully scanned gives the more realistic results.
I notice that the count for AWs and WWs is the same in both views - that's strange, as I sometimes partially scan systems and get AWs that are close to the range ELWs, or I scan some WWs for the credits. But in either case I might not fully scan the system - these bodies from not fully scanned systems should not be counted in the view. Thus I would expect different total values of AWs and tWWs for the CC-K boxel, but they list the same 20 AWs and 104 tWWs.
Of course, the fully scanned result is also somewhat skewed by the star-only systems, but that's the nature of my otherwise sloppy exploration process, so all fine. That said, I wonder whether a column for star-only systems would have any value (number of systems, ratio to visited, avg number of stars), not sure...
All visited systems count:
Only the fully FSS scanned systems count:
Interesting are the columns regarding ELWs, AWs, tWWs, tHMCs. As I always fully scan the ELW systems, that result is correct in the all visited view, but skewed in the fully scanned statistic, while for the others the fully scanned gives the more realistic results.
I notice that the count for AWs and WWs is the same in both views - that's strange, as I sometimes partially scan systems and get AWs that are close to the range ELWs, or I scan some WWs for the credits. But in either case I might not fully scan the system - these bodies from not fully scanned systems should not be counted in the view. Thus I would expect different total values of AWs and tWWs for the CC-K boxel, but they list the same 20 AWs and 104 tWWs.
Of course, the fully scanned result is also somewhat skewed by the star-only systems, but that's the nature of my otherwise sloppy exploration process, so all fine. That said, I wonder whether a column for star-only systems would have any value (number of systems, ratio to visited, avg number of stars), not sure...
Yeh, the counts are what I mentioned in previous post - I'm not sure which is more useful knowing that a particular boxel had 12 TFWWs, or that it only had 10 in the systems fully scanned. I went back and forth on this and decided it was better to display 12. You can see this in DC-K d9 - you've seen 12 TFWWs there, but when only looking at fully scanned the ratio is 1/22.20 - and given there were 222 fully scanned systems we can tell that only 10 of the 12 TFWWs were in fully scanned systems. So the information is there, just... obfuscated. If I just showed 10, I think that is misrepresentative the other way - a better example would be ELWs, I'll usually fully scan an ELW system but if it's already fully scanned by another commander and I'm in a hurry I sometimes don't bother. I think in that case it is wrong to not show the actual ELW count.
But thanks for the feedback - I will ponder it more and see if I can't find a way to display all the information without making it too ugly
I think I know what this is, and if I'm right it'll be a trivial fix. I will try and find some time later this week to poke it with a stick.
I know this is off-topic, but could someone please explain t me how boxels in ED work and how can I use this knowledge and Matts plugin to increase my chances of finding ELWs?
Thank you!
Thank you!
On this page of the Great ELW Fishing Expedition there are some posts on the subject, also linking to more detailed information.
As for the usefulness of the BoxelStats plugin, it provides you with your hit ratio, better than 1 in 40 is good, worse than 1 in 50 you better check a different boxel (assuming a reasonable sample size of a few hundred systems visited).
There is also the subject of "metallicity" (for our purpose and in the game context rated by the Helium content of GGs), explained by marx in this post (and linked thread). Systems in a boxel share a similar He%. As for the plugin, it's in the last three columns (see my screenshots above), min. He%, max. He%, and possible He% range for the boxel. There is a higher likelihood of more ELWs in a boxel with lower He%, lower 25% range and under is good, but it is no guarantee.
In the screenshots above you see me probing different boxels, and you also see for the same metallicity of ~25.2% the widely different ELW hitrates of 1 in 57 for the DC-K and 1 in 31 for the CC-K boxel.
Last edited:
Thank you, I will read the threads and posts you linked and hopefully will understand what the boxel is and how to plot a route within certain boxels with higher probability...
You can give EDJP a shot as well. It has a Boxel Explorer, which will show you where your current boxel is in relation to the sector - and you can navigate to other boxels within the sector. It also has a Boxel Survey mode that will keep putting the next system in the boxel on your clipboard ready for pasting into the Galaxy Map (it will also stop you visiting systems you've already been to, and optionally, anything already in EDSM). Hit 50-100 systems in a boxel, if your ELW ratio is good then keep going - otherwise, find a new boxel and start a survey there.
Amazing! Thank you!
I've had a quick check of the plugins against the new release of Observatory Core, and at first glance everything seems to be working as expected. I do want to get new versions built against the new version of Framework but don't have a lot of free time at the moment to get on top of it - it'll happen, but not immediately.
In the interim, if anyone notices any oddness with my plugins and the new ObsCore release then please let me know and I'll investigate.
In the interim, if anyone notices any oddness with my plugins and the new ObsCore release then please let me know and I'll investigate.
It seems to work the same.
I still have the problem of the distance notification being unreliable -- sometimes works, sometimes not -- but I had that before, too.
So, no change that I can see.
The "you've travelled X meters from last sample" message, you mean? Not sure that's been reported previously - anyone else having this issue?
rootsrat
Volunteer Moderator
Sounds very interesting! Massive kudos. I love Observatory and its about to get even better.
Best community ever ❤
o7
Yes that one. If it stops working I toggle the notification checkbox, and then it seems to start working again. I log off and on fairly often sometimes. That may have something to do with it.
Updated BioInsights. Fixes include:
Probably other things but I forget.
- UI updates on juicing, not just SRV interaction
- Clypeus should notify for distances now
- Now uses non-localised genus/species so all elements should work in all languages (though reporting still English for now)
- Optional notification for base value / sample distance when encountering species for first time on a body actually works now
- Built against latest Observatory Framework
Probably other things but I forget.
Updated BoxelStats. Updates include:
- Optionally, hide boxels not visited in last x weeks (set to 0 to disable)
- Added a button in Settings to redraw UI - changing options in settings doesn't automatically update the output, this button fixes that
- Added a button in Settings to check if there's a newer version available.
- Split counts and averages into different fields in output
- When choosing "Complete Systems Only", counts will not include valid objects from systems that were not fully scanned.
- Built against latest Observatory Framework