Welcome, Guest
Please Login or Register.    Lost Password?

Anomalies marked Empty - Ignores Renewed Anomaly
(0 viewing) 
Go to bottomPage: 1
TOPIC: Anomalies marked Empty - Ignores Renewed Anomaly
#29798
Anomalies marked Empty - Ignores Renewed Anomaly 7 Years, 11 Months ago Karma: 0
Slav,

I couldn't figure out why the bot would only go through 1 rotation before becoming useless sitting in the station, but I think I found the problem. When the bot finishes a site, it marks that site as empty and avoids it the next time around. I found this in my log, which is scanning for a "Forsaken Hub" or "Guristas Forsaken Hub" and finds one on Scan 7/17 as shown below.

Code:

     
     13:09:17 (4321) Scan Result: 6/17: PosIndex: 5, ID: redacted, D: 11.92 AU, ScanGroup: Cosmic Anomaly, Group: Combat Site, Name: Guristas Forlorn Hub, Func : CheckAnomalies
     13:09:17 (4321) Checking keywords (2) :, Func : CheckAnomalies
     13:09:17 (4321) |Forsaken Hub|, Func : CheckAnomalies
     13:09:17 (4321) |Guristas Forsaken Hub|, Func : CheckAnomalies
     13:09:17 (4321) Anomaly name: Guristas Forlorn Hub, Func : CheckAnomalies
     13:09:17 (4321) Is Wrong Keyword, next..., Func : CheckAnomalies
     13:09:17 (4321) Scan Result: 7/17: PosIndex: 6, ID: redacted, D: 2.74 AU, ScanGroup: Cosmic Anomaly, Group: Combat Site, Name: Guristas Forsaken Hub, Func : CheckAnomalies
     13:09:17 (4321) Is Empty, next..., Func : CheckAnomalies
     13:09:17 (4321) Scan Result: 8/17: PosIndex: 7, ID: redacted, D: 1.29 AU, ScanGroup: Cosmic Anomaly, Group: Combat Site, Name: Guristas Forlorn Hub, Func : CheckAnomalies
     13:09:17 (4321) Checking keywords (2) :, Func : CheckAnomalies
     13:09:17 (4321) |Forsaken Hub|, Func : CheckAnomalies
     13:09:17 (4321) |Guristas Forsaken Hub|, Func : CheckAnomalies
     13:09:17 (4321) Anomaly name: Guristas Forlorn Hub, Func : CheckAnomalies
     13:09:17 (4321) Is Wrong Keyword, next..., Func : CheckAnomalies



So Scan 7/17 found the Guristas Forsaken Hub, but said the anomaly is empty.. So I opened up Anomaly.xml and found this:
Code:

  <AnomalyTable>
    <id>redacted</id>
    <name>Guristas Forsaken Hub</name>
    <scanDateUtc>2013-11-xxx</scanDateUtc>
    <isEmpty>true</isEmpty>
  </AnomalyTable>



So, once the bot finishes a site, it marks that specific Anomaly ID (ie. RXI-137) as empty. The problem is in Null, once a site is completed and the area abandoned, the site ID will refresh and have a new set of rats when it appears on the scanner again.



Suggestion:
Create a setting for null to not mark sites as empty at all, or a setting to flush the AnomalyTable every X minutes.

Also, my area has more than 17 anomalies, so adding the option to scroll would be nice too. I'd think scroll to the bottom, then start scanning from the bottom up until it reaches the Anomaly ID of the 17th one?
texas32
Fresh Boarder
Posts: 2
graphgraph
User Offline Click here to see the profile of this user
Last Edit: 2013/11/17 13:58 By texas32.
The administrator has disabled public write access.
 
#29801
Re: Anomalies marked Empty - Ignores Renewed Anomaly 7 Years, 11 Months ago Karma: 757
Thank you for this, I was not aware that one anomaly may be renewed under the same name. How long time is required to empty anomaly disappear? I think 1 hour should be ok. I will add this correction to the next version.

I will try to use whole height of the eve client window. Just need to make sure that bot is not checking HP status bar during anomaly scan. I think everybody can live without HP scanning during anomaly scanning.
Slav2
Admin
Posts: 15802
graph
User Offline Click here to see the profile of this user
Last Edit: 2013/11/17 16:08 By Slav2.
The administrator has disabled public write access.
Send logs to my mail - with subject 'log files' to pass spam filter.
How to record logs in knowledge base
 
#29802
Re: Anomalies marked Empty - Ignores Renewed Anomaly 7 Years, 11 Months ago Karma: 0
I would recommend allowing it to be a custom option. I'm running a forsaken hub every 20-40 minutes, with 3 in system, but only 2 that appear to the bot. If I blow through both of the ones the bot can detect, I might get stuck and waste time since the bot still thinks they're empty.

Alternatively, if I'm trying to blitz through lower level ones, I'd like to reduce the refresh to maybe 15-20 minutes.

1 hour should work and keep the bot productive, but I think a custom option would be the most useful - since we would be able to adjust it to the length of time it takes for each person to finish a site.
texas32
Fresh Boarder
Posts: 2
graphgraph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
#29803
Re: Anomalies marked Empty - Ignores Renewed Anomaly 7 Years, 11 Months ago Karma: 757
I think the is coincidence that new anomaly resped under the same name. Or you believe this is quite frequent coincidence? Lets do one hour, and if you will find any problem, I will make this timer custom
Slav2
Admin
Posts: 15802
graph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
Send logs to my mail - with subject 'log files' to pass spam filter.
How to record logs in knowledge base
 
Go to topPage: 1
Moderators: Slav2
© Macro Laboratory 2021
All rights reserved!
Design by Ivan Kozyrin