Release Artemis Scanner Tracker: A EDMC plugin that keeps track of the exobiology scanner of a CMDRs Artemis suit

[Balvald]

Release of v0.2.7

New in this one:

• The plugin now tells you how many exobiological signals can be found on the planet that you're on and how many you've finished. Ref: #36
• The plugin also tells you which plants you've already scanned from the planet that your currently on by setting the names of the respective species in green while you're on said planet.
  Well it says here "while you're on said planet", it actually suffices to be in orbital cruise aka being pretty close to a planet
• A bugfix regarding the tracking of the worth of unsold exobiological data while using multiple CMDRs

Latest Release

 

[CMDR ArthritisGuy]

How do I find the output from ArtemisTracker? Right now EDMC is struggling to login, and the plugin is installed where the options menu takes me. Any input is appreciated!

 

[Balvald]

@CMDR ArthritisGuy

How do I find the output from ArtemisTracker? Right now EDMC is struggling to login, and the plugin is installed where the options menu takes me. Any input is appreciated!

Not sure what you specifically mean with output. What the plugin shows on the main ui?

Check which version of EDMC you have installed.

(specifically 5.9.2 broke a few of plugins I think, I'm not sure if mine is one of them)
If its 5.9.2 go update it to 5.9.3.
5.9.1 and earlier should work fine.

If its not that check the installation again.

When installed properly it should show a register called AST that takes you to the options and the main ui will appear on the edmc window:

Make sure its installed in:

%localappdata%\EDMarketConnector\plugins

as in in that folder is a Folder called anything resebling AtermisScannerTracker and inside there is a load.py
easiest way is to extract it into its own folder and then move it

Anything that the plugin saves can be also found in its folder.

%localappdata%\EDMarketConnector\plugins\ArtermisScannerTracker-0.2.7

(version number in the folders name is optional)
inside it should look something like this:

pycache and the *.json files should appear on their own after you start edmc with the plugin installed.

If this hasn't helped or your not on Windows I'd like to see the edmc log for the startup.

 

[CMDR ArthritisGuy]

Thanks for the reply.

AST folder attached. Never ran, by the looks of it.
Plugins folder that i went to (the first directory you said) is attached.
EDMC install folder attached. Honestly confused. its never logging in either. Theres no logs or anything, its silly! I've ran EDMC around 2 mins before taking the screenshots just to see if something changed. Apologies if I seem short, this is my fourth time typing this up, first 3 got lost.

 

[Balvald]

@CMDR ArthritisGuy

Sounds weird. I'd like to see the log that edmc produces.

Should be at:

%TEMP%\EDMarketConnector.log

Normally it does not stop edmc to appear even if something were wrong with the plugin.
I could check over it sometime tomorrow.

 

[CMDR ArthritisGuy]

Here ya go! Ridiculously short, just copy-pasted for being so short.

2023-08-06 21:20:21.380 UTC - INFO - 182728:183468:183468 journal_lock.JournalLock._obtain_lock:106: Exception: Couldn't lock journal directory "C:\Users\Arthr\Saved Games\Frontier Developments\Elite Dangerous", assuming another process running: PermissionError(13, 'Permission denied')
2023-08-06 21:20:21.382 UTC - INFO - 182728:183468:183468 EDMarketConnector.main:359: An EDMarketConnector.exe process was already running, exiting.
2023-08-06 21:31:40.032 UTC - INFO - 183200:183208:183208 monitor.EDLogs.start:262: Monitoring Journal Folder: "C:\Users\Arthr\Saved Games\Frontier Developments\Elite Dangerous"
2023-08-06 21:31:40.036 UTC - INFO - 183200:183208:183208 monitor.EDLogs.start:263: Start Journal File: "C:\Users\Arthr\Saved Games\Frontier Developments\Elite Dangerous\Journal.2023-08-06T135909.01.log"
2023-08-06 21:31:40.047 UTC - ERROR - 183200:183208:183208 companion.Auth.refresh:384: Frontier CAPI Auth: No token for "ARTHRITISGUY"
2023-08-06 21:31:40.047 UTC - INFO - 183200:183208:183208 companion.Auth.refresh:387: Frontier CAPI Auth: New authorization request
2023-08-06 21:31:40.049 UTC - INFO - 183200:183208:183208 companion.Auth.refresh:393: Trying auth from scratch for Commander "ARTHRITISGUY"
2023-08-06 21:31:44.122 UTC - INFO - 183200:183208:183208 EDMarketConnector.AppWindow.onexit:1954: Starting shutdown procedures...
2023-08-06 21:31:44.124 UTC - INFO - 183200:183208:183208 EDMarketConnector.AppWindow.onexit:1957: Closing update checker...
2023-08-06 21:31:44.125 UTC - INFO - 183200:183208:183208 EDMarketConnector.AppWindow.onexit:1964: Notifying plugins to stop...
2023-08-06 21:31:44.126 UTC - INFO - 183200:183208:183208 plug.notify_stop:243: Asking plugin "EDDN" to stop...
2023-08-06 21:31:44.130 UTC - INFO - 183200:183208:183208 plug.notify_stop:243: Asking plugin "EDSM" to stop...
2023-08-06 21:31:44.136 UTC - INFO - 183200:183208:183208 plug.notify_stop:243: Asking plugin "Inara" to stop...
2023-08-06 21:31:44.138 UTC - INFO - 183200:183208:183208 plug.notify_stop:249: Done
2023-08-06 21:31:44.139 UTC - INFO - 183200:183208:183208 EDMarketConnector.AppWindow.onexit:1969: Unregistering hotkey manager...
2023-08-06 21:31:44.142 UTC - INFO - 183200:183208:183208 EDMarketConnector.AppWindow.onexit:1973: Closing CAPI query thread...
2023-08-06 21:31:44.143 UTC - INFO - 183200:183208:183208 EDMarketConnector.AppWindow.onexit:1977: Closing dashboard...
2023-08-06 21:31:44.145 UTC - INFO - 183200:183220:183220 companion.Session.capi_query_worker:966: endpoint __EDMC_WORKER_SHUTDOWN, exiting...
2023-08-06 21:31:44.146 UTC - INFO - 183200:183220:183220 companion.Session.capi_query_worker:1009: CAPI worker thread DONE
2023-08-06 21:31:44.155 UTC - INFO - 183200:183208:183208 EDMarketConnector.AppWindow.onexit:1980: Closing journal monitor...
2023-08-06 21:31:44.165 UTC - INFO - 183200:183208:183208 EDMarketConnector.AppWindow.onexit:1984: Closing protocol handler...
2023-08-06 21:31:44.166 UTC - INFO - 183200:183208:183208 EDMarketConnector.AppWindow.onexit:1987: Closing Frontier CAPI sessions...
2023-08-06 21:31:44.167 UTC - INFO - 183200:183208:183208 EDMarketConnector.AppWindow.onexit:1991: Closing config...
2023-08-06 21:31:44.168 UTC - INFO - 183200:183208:183208 EDMarketConnector.AppWindow.onexit:1994: Destroying app window...
2023-08-06 21:31:44.245 UTC - INFO - 183200:183208:183208 EDMarketConnector.AppWindow.onexit:1997: Done.
2023-08-06 21:31:44.246 UTC - INFO - 183200:183208:183208 EDMarketConnector.main:2306: Exiting

 

[Balvald]

@CMDR ArthritisGuy

Thanks for the reply.

AST folder attached. Never ran, by the looks of it.
Plugins folder that i went to (the first directory you said) is attached.
EDMC install folder attached. Honestly confused. its never logging in either. Theres no logs or anything, its silly! I've ran EDMC around 2 mins before taking the screenshots just to see if something changed. Apologies if I seem short, this is my fourth time typing this up, first 3 got lost.
View attachment 363565
View attachment 363564View attachment 363563

I see what may be the problem now. The files of the plugin are one folder too deep. they are in "%localappdata%/plugins/AST-0.2.7/AST-0.2.7/" instead of "%localappdata%/plugins/AST-0.2.7/" (Shortened plugin name for convenience)
From the last picture just move everything one folder above and it should work

 

[CMDR ArthritisGuy]

So! I fixed both the ArtemisScannerTracker with your thing above, thanks!
EDMC just... didnt work. Updating, once the update was released, helped. I was in the "subset of users" that couldnt authenticate with the API for whatever reason. Time to get that data!

 

[CMDR Wuppy]

Hi, firstly, this plugin is pretty neat so far, thanks for setting it up. Secondly, I'm currently out in the black and have scanned quite a few plants before I downloaded the plugin. the estimated value is currently only reading the value of one scanned plant. I have tried both scan journal buttons in the settings, but I cannot get it to load the scan values for the previous plants. Is there a way to get it to do that?

Again, thanks for the plugin, so far it is looking to be very helpful for my exobio.

 

[Balvald]

Hi, firstly, this plugin is pretty neat so far, thanks for setting it up. Secondly, I'm currently out in the black and have scanned quite a few plants before I downloaded the plugin. the estimated value is currently only reading the value of one scanned plant. I have tried both scan journal buttons in the settings, but I cannot get it to load the scan values for the previous plants. Is there a way to get it to do that?

Again, thanks for the plugin, so far it is looking to be very helpful for my exobio.

Is that single plant the only one mentioned in notsoldbiodata.json?
Also what OS are you running Windows or some form of Linux?

The two buttons are only different in case of the location they go through the journal files. (local is the journal folder insode the folder where the plugin sits) The other one is where edmc reads the journals from.

Theres a few possibilities whats going on since I don't have the full picture:
1. The journal files that you got only go that far back.
2. The journal files go that far back but the plugin somehow gets the wrong path (either edmc is set up wrong or a bug in the plugin somewhere)
3. Its a bug related to this: https://github.com/Balvald/ArtemisScannerTracker/issues/48 at which point I'd like to see said journal files to see if I can reproduce the behaviour.

Tick the box for debug mode in the AST settings so when you use the journal buttons it'll record everything the plugin is doing so I can check if it breaks anywhere/does anything weird when I read through the logs.

Possible user-side hotfix: copy your journal files (like from your journal limpet if you have that set up) in the local journal folder and try with that button if it works/behaves different then its 2.

Though I kind of hope its case 3 on this one so I can finally get a hold of that bug.

 

[CMDR Wuppy]

Is that single plant the only one mentioned in notsoldbiodata.json?
Also what OS are you running Windows or some form of Linux?

The two buttons are only different in case of the location they go through the journal files. (local is the journal folder insode the folder where the plugin sits) The other one is where edmc reads the journals from.

Theres a few possibilities whats going on since I don't have the full picture:
1. The journal files that you got only go that far back.
2. The journal files go that far back but the plugin somehow gets the wrong path (either edmc is set up wrong or a bug in the plugin somewhere)
3. Its a bug related to this: https://github.com/Balvald/ArtemisScannerTracker/issues/48 at which point I'd like to see said journal files to see if I can reproduce the behaviour.

Tick the box for debug mode in the AST settings so when you use the journal buttons it'll record everything the plugin is doing so I can check if it breaks anywhere/does anything weird when I read through the logs.

Possible user-side hotfix: copy your journal files (like from your journal limpet if you have that set up) in the local journal folder and try with that button if it works/behaves different then its 2.

Though I kind of hope its case 3 on this one so I can finally get a hold of that bug.

There are only the plants I have scanned since installing the plugin (4 at the time of this post) currently in the notsoldbiodata.json. I noticed that the soldbiodata.json has a whole bunch of scans that I am pretty sure are currently unsold. I can check a couple system names the verify that though.

I am on windows 10 home.

1. I have journal files going back a year or two i believe.
2. I have copied the journals to the local journal folder and tried both scan buttons but no luck.
3. Do you want me to DM you the journals and the logs? where are the logs located typically?

I've also got the debug box checked, just not sure where to find the file to send to you.

Thanks for taking the time to help me with this, I appreciate it.

 

[Balvald]

There are only the plants I have scanned since installing the plugin (4 at the time of this post) currently in the notsoldbiodata.json. I noticed that the soldbiodata.json has a whole bunch of scans that I am pretty sure are currently unsold. I can check a couple system names the verify that though.

I am on windows 10 home.

1. I have journal files going back a year or two i believe.
2. I have copied the journals to the local journal folder and tried both scan buttons but no luck.
3. Do you want me to DM you the journals and the logs? where are the logs located typically?

I've also got the debug box checked, just not sure where to find the file to send to you.

Thanks for taking the time to help me with this, I appreciate it.

Alright sounds like its not a problem of just of it just not properly calculating the amount thats left unsold.
would be nice to know if some did slip into soldbiodata.json for some reason (that'd be a new one)

After checking the debug box just press the journal button once more just to be safe.
(unless you already did press both)

1. good its not the trivial case.
2. alright so the behaviour falls squarely into the domain of that ol bug I couldn't reproduce before.
3. Yes please I'd like one dataset to rummage through so that bug gets squashed, edmc logs are located in:

 %TEMP%\EDMarketConnector\EDMarketConnector-debug.log

In case of these log files please send I guess the whole bunch from EDMarketConnector-debug.log to EDMarketConnector-debug.log.10.
The journal crawling can create an awful lot of logging statements while in debug mode. (some more useful than others depending on situation) to put in the logs and each log is limited to just ~1MB and with it going through two years worth of journals it could be its filling atleast half of them. It mostly depends how much scanning has been done so I can't estimate that well. Generally if the timestamp in that log file is not too far back from when you pressed the journal crawling buttons just include it.

 

[Balvald]

Release of v0.2.8:

New in this one:

• Bugfix for the Journal Crawling: Anyone that has died in Horizons and used the journal crawling buttons before and really values the consistency of his sold and unsold data should redo the journal crawling to retrieve plants that the plugin may have dismissed in the past. Ref: #48

That one death in Horizons from 2021 really came to haunt you here

Latest Release

 

[Balvald]

Release of v0.2.9:

New in this one:

• Plugin now uses cross-platform compatible paths. Ref: #58

Latest Release

 

[Zven Tveskoeg]

Hi and thank you for your work!
I was searching for this because I'm on way for Xenobiology (love discoveries by the past without Odyssey).
I've just installed your plugin and it works well but another question, I've already discovered 4 species yesterday, could I have a way to initialize with them to have them on the historic ? Or does it work just now and for futur discoveries?

 

[Balvald]

Hi and thank you for your work!
I was searching for this because I'm on way for Xenobiology (love discoveries by the past without Odyssey).
I've just installed your plugin and it works well but another question, I've already discovered 4 species yesterday, could I have a way to initialize with them to have them on the historic ? Or does it work just now and for futur discoveries?

This is where you go into the settings and AST tab and press the "scan game journals for exobiology" button (edmc may seem to lock up for a few seconds) but once its done it will show up on the plugin if you're in the system.
Because what you described already exists c:

 

[Zven Tveskoeg]

Allright thank you very much =D

 

[CMDR Yojimbosan]

EDMC on my machine has just updated to 5.11.1+5d43388
Now AST doesn't seem to be able to display clonal distances & last scan locations.
EDMC's debug logs are full of :-

2024-06-12 08:37:42.189 UTC - DEBUG - 20372:14460:14460 plugins.inara.try_send_data:1602: Sending data to API, attempt #1
2024-06-12 08:37:42.613 UTC - ERROR - 20372:20736:20736 plug.notify_dashboard_entry:387: Plugin "AST" failed
Traceback (most recent call last):
  File "plug.pyc", line 384, in notify_dashboard_entry
  File "C:\Users\xbox\AppData\Local\EDMarketConnector\plugins\ArtemisScannerTracker-0.2.9\load.py", line 127, in dashboard_entry
    plugin.AST_num_bios_on_planet = plugin.AST_bios_on_planet[key]
                                    ~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^
TypeError: 'NoneType' object is not subscriptable

 

[Balvald]

EDMC on my machine has just updated to 5.11.1+5d43388
Now AST doesn't seem to be able to display clonal distances & last scan locations.
EDMC's debug logs are full of :-

2024-06-12 08:37:42.189 UTC - DEBUG - 20372:14460:14460 plugins.inara.try_send_data:1602: Sending data to API, attempt #1
2024-06-12 08:37:42.613 UTC - ERROR - 20372:20736:20736 plug.notify_dashboard_entry:387: Plugin "AST" failed
Traceback (most recent call last):
  File "plug.pyc", line 384, in notify_dashboard_entry
  File "C:\Users\xbox\AppData\Local\EDMarketConnector\plugins\ArtemisScannerTracker-0.2.9\load.py", line 127, in dashboard_entry
    plugin.AST_num_bios_on_planet = plugin.AST_bios_on_planet[key]
                                    ~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^
TypeError: 'NoneType' object is not subscriptable

Just checked why that is.
The api that is used/asked how many bio signals are on each of the planets upon entering a system instead answers with something different that I seem to not have expected.
(this is what ends up creating the error message in the codeblock.)
(also I have to ask whats up with it because it currently doesn't seem to find anything, even for systems that definitely worked in the past. Seems like api is dead :c)

This ends up creating a different type of error (in this case a TypeError) that I don't handle currently.
Then it crashes out the function just before it can do the clonal distances.

I'll make a hotfix for it later today, test if it works again and then get another release.
This will also mean that the plugin itself won't be able to say how many different bio signals are on a planet for a lot of planets unless you did a dss scan on it for the first time in the very same session.

 

[Balvald]

Release of v0.3.0

New in this one:

• Hotfix: Plugin now ignores a certain API which is now presumed to be dead and an EX-API. or its just resting
• New Feature: Plugin now has an additional window through which one can look at already scanned biodata, without the need to fly to the system of said biodata. Ref: #59