| Pages: [1] :: one page |
| Author |
Topic |
Tiberius Xavier
Eternity INC.
Project Alice.
    |
Posted - 2008.05.28 17:31:00 -
[1]
I tried searching for this topic but had no luck finding a solution. With the API and the Trinity 1.1 DB dump, I can figure out most of what I want. But all this falls short of a couple pieces of information.
Is there a way (either via the Assets / StarbaseDetails / whatever) to figure out which modules are anchored/online/incapped at a POS? Alternatively, is there a way to accurately determine the fuel consumption rate outside of (less reliable) manual intervention?
Thanks.
|
Tiberius Xavier
Eternity INC.
Project Alice.
|
Posted - 2008.05.28 17:31:00 -
[2]
I tried searching for this topic but had no luck finding a solution. With the API and the Trinity 1.1 DB dump, I can figure out most of what I want. But all this falls short of a couple pieces of information.
Is there a way (either via the Assets / StarbaseDetails / whatever) to figure out which modules are anchored/online/incapped at a POS? Alternatively, is there a way to accurately determine the fuel consumption rate outside of (less reliable) manual intervention?
Thanks.
|
Salvis Tallan
The Shadow Order
SMASH Alliance
|
Posted - 2008.05.28 18:17:00 -
[3]
short answer, No.
Longer answer, No api has details linking the starbase mods to the tower because that data isnt stored in the database, blah blah....
On the other hand, you can take a list of towers, compare that to corp assets in space in the same system that are pos items, then by tracking what is in each module, like ammo, blueprints, etc. have the user set up what towers are where, at which point you save that info and they will hopefully not have to do it again. |
Tiberius Xavier
Eternity INC.
Project Alice.
|
Posted - 2008.05.28 18:24:00 -
[4]
Right, but is there any way of getting the status of the modules? The AssetList will not 'flag' it as anchored or onlined, etc. That makes fuel usage calculations difficult (using a delta from the previous API call) which is still deficient if more modules are (un)anchored, destroyed, etc. |
Ausser
Cybertech Industrials Agency
|
Posted - 2008.05.28 21:45:00 -
[5]
There is no simple way to do this for cpu/power related fuel.
For fuel marked 'Online' you can look up fuel consumption per hour in invControlTowerResources for your tower type.
Best practice of fuel calculation
Best practice to calculate fuel consumption for CPU/Power fuel is to compare the values returned by your daily calls to StarbaseDetails.xml.aspx:
- If you have more fuel than yesterday, some maintenance was done on the tower (at least fuel refill). The maintainer may also changed the configuration. So keep these values and calculate consumption next day.
- If you have less fuel than yesterday, use the call timestamps to calculate the duration between calls. Then you can backpredict the CPU/Power of the configuration by dividing with invControlTowerResources values. This will give you a hint if configuration changed. You can also calculate what your tower consumes per hour. Keep these values and compare them next day again. So you can estimate when your tower runs out of fuel.
The unusual way to get pos inventories
Maybe there is another way, which i didnt tested. It sounds dubious but it could work, even if it needs lots of investigation:
Take a look on the files in machonet cache, and what the log server writes to disk.
When using a scanner ingame near your pos, you get scan results of your anchored modules in your client. These could maybe be written to cache/logserver. You could write a small tool looking for that data and uploading it to your database. This would not give you online/offline status. On the other hand, a list of modules is better than nothing. If all your ally members use this tool each time after they maintain a tower, then you end up with accurate inventory of pos modules.
You could also implement a small web form to capture online/offline status. Use the data from scanning, which has been uploaded to your server, to display an igb page with a list of modules at that pos. The maintainer who has uploaded the data may now access that page ingame and select the checkboxes which modules are online/offline/unanchored. This could also be implemented without a central web server by using one on localhost. The ability of the igb to supply location information (together with the ip) is also handy to select the right set of scan results.
I like the idea of scan data processing, because it involves some role playing to get all that data. However, i dont know if this approach would work at all. I plan to look at it as soon as i get some time. Atm, i dont know if client/logserver spits out scan data to harddisk at all.
If somebody has allready tried this (or something similar) - any comments/suggestions/thoughts/hints/code-samples are welcome 
|
Ki Tarra
Ki Tech Industries
|
Posted - 2008.05.28 23:03:00 -
[6]
It is not possible for the API to pull up POS module information because of the way the database is currently structured.
I tried to find the original dev explination, but I am not sure where the thread for that was.
As far as I remember, the explination is that POS modules are not associated with the POS tower in the database. Instead, when the solar system is loaded to a node, the details of all the POS modules anchored in the system are loaded. The node will then sort out what is active, etc. Because the API server access the database not the node and it is unable to reproduce all of the processing that the node completes when it loads, the API is unable to provide POS module information.
As for the problem of projecting POS fuel consumption: I would recommend that you log POS fuel levels over an interval, say 24 hours. You can then use the difference in fuel levels between that interval to project fuel levels that far into the future.
The arguement that the above method is inacturate because modules might be onlined or offlined is rendered pointless by the observation that any module status information would be subject to the same level of caching as the POS fuel levels.
The main complication is the requirement to record POS fuel levels for future reference.
Secondary, you need to make sure that you poll the server with proper regularity, or properly adjust for irregular polling. IE, if fuel is consummed every hour, polling the fuel levels every 2.5 hours will result in half of your readings showing 2x hourly consumption and half showing 3x hourly consumption. That problem is easily avoided by controlling the polling frequency: ie only poll on integer multiples of the rate of fuel consumption.
|
Ausser
Cybertech Industrials Agency
|
Posted - 2008.05.30 13:56:00 -
[7]
Posting ideas for a tool is one thing, another is to wait till someone moves and implements it. I dont need the pos data by myself, but i think there are many ppl who would be happy about. So i move my botty for you and start writing a pos inventory aquisition tool.
POS Scanner - progress
The management details would be best since they must contain information about module status. However, i cannot find scan data or management details in machonet cache (maybe i've missed it, i dont have a parser for these files atm).
But the onboard scanner request/result shows up on logserver logs. That's good news. The bad one is: The scan result in the logs seems to be truncated, and it is binary, not easy to read.
Yesterday night i took a look on the log server file format. Its binary, some details are hard to find out. I've figured out most of the important details allready. A parser can be done. This will take some days.
As soon as i get this running i will take a look on the scan result message data. It's binary too, in an unknown format, and its truncated. The messages which are used by tools like BACON are much easier to read because they are in plain text instead of binary data. But i'm sure parsing the scan result messages can be done.
So it is still to early to tell if we end up with a simple tool which dumps nice xml scan results to some directory.
Any comments/suggestions/thoughts are welcome 
|
Tiberius Xavier
Eternity INC.
Project Alice.
|
Posted - 2008.05.30 14:13:00 -
[8]
 Originally by: Ausser
Posting ideas for a tool is one thing, another is to wait till someone moves and implements it. I dont need the pos data by myself, but i think there are many ppl who would be happy about. So i move my botty for you and start writing a pos inventory aquisition tool.
POS Scanner - progress
The management details would be best since they must contain information about module status. However, i cannot find scan data or management details in machonet cache (maybe i've missed it, i dont have a parser for these files atm).
But the onboard scanner request/result shows up on logserver logs. That's good news. The bad one is: The scan result in the logs seems to be truncated, and it is binary, not easy to read.
Yesterday night i took a look on the log server file format. Its binary, some details are hard to find out. I've figured out most of the important details allready. A parser can be done. This will take some days.
As soon as i get this running i will take a look on the scan result message data. It's binary too, in an unknown format, and its truncated. The messages which are used by tools like BACON are much easier to read because they are in plain text instead of binary data. But i'm sure parsing the scan result messages can be done.
So it is still to early to tell if we end up with a simple tool which dumps nice xml scan results to some directory.
Any comments/suggestions/thoughts are welcome
Interesting approach, Ausser. I never consider parsing log files as a solution. I'd be interested in seeing the results.
I have decided to make my own open-sourced version for this. I am not entirely satisfied with all the POS setup and monitoring tools right now. My first step is trying to get libeveapi patched, but if I don't get any progress there, I will just branch a private version off that and incorporate a static extraction from the SQLite3 port.
|
Salvis Tallan
The Shadow Order
SMASH Alliance
|
Posted - 2008.05.30 14:35:00 -
[9]
Originally by: Ausser
POS Scanner - progress
The management details would be best since they must contain information about module status. However, i cannot find scan data or management details in machonet cache (maybe i've missed it, i dont have a parser for these files atm).
But the onboard scanner request/result shows up on logserver logs. That's good news. The bad one is: The scan result in the logs seems to be truncated, and it is binary, not easy to read.
Scan data is not saved as a cache file :(
I havent looked at the logserver stuff, so I cannot tell you what might be there, but truncation might not be a problem if you only scan for the pos modules within like 100km.
------
 |
Ausser
Cybertech Industrials Agency
|
Posted - 2008.06.03 02:19:00 -
[10]
POS Scanner News
The first preliminary release of a logserver tool library is out. Please read here for more details:
http://myeve.eve-online.com/ingameboard.asp?a=topic&threadID=787504
The next step will be to implement the missing features. Thereafter the POS Scan Tool can be built.
I'll continue posting POS Scanner related stuff here, while logserver related stuff will go into the other thread.
Any comments and thoughts are welcome.
|
|
DeTox MinRohim
Madhatters Inc.
Pure.
|
Posted - 2008.06.03 13:52:00 -
[11]
Althouh that's a step, I still can't see it as efficient for big alliances having hundreds of POS throughout the universe.
It doesn't change the workload of going to all the POS (or near) to scan them. Once you're there, you can simply open the "Manage" window and do the work of adding them.
Note also that the scan results doesn't give you the owner of the POS unlike when you fly to it.
Still think Devs can hit their head a bit more so that the nodes do an export of the linked mods when going live. 
------
This sig space is Read-only !
omgalink - Online Skillsheet |
|
| Pages: [1] :: one page |
| First page | Previous page | Next page | Last page |