Jump Freighter Kill Statistics

I’ve been working with @Lockefox over the past few days to setup his Eve-Prosper zKillboard scraper on my Raspberry Pi LAMP instance that I have in my home lab in order to do some data analysis.

IMG_20131203_211739-1

Let there be Database Rows

The only edits that I had to make to the project code were the database connection details in scraper.ini and a narrowing down of ship classes listed in toaster_shiplist.json. After getting the data into mySQL and importing the invTypes and mapSolarSystems tables from the static dump into my database, I could start to filter and sort the results.

Kicking off the scraper:

pi@charon ~/eve_prosper $ python zkb_scraper.py — startdate=2013-12-01
DB Connection:          GOOD
zKillboard connection:  GOOD
no crash log found.  Executing as normal
Parsed Capital Industrial Ship: [200, 29713239, 0, ‘2013-04-08’] sleep=20.0
Parsed Capital Industrial Ship: [290, 27468307, 1, ‘2012-12-30’] sleep=20.0

Here is the query to get Racial JFs and also include the solar system name and security value:

— Get Racial JFs
SELECT destruction_data.date, destruction_data.week, destruction_data.typeID, destruction_data.systemID, destruction_data.destroyed, invTypes.typeName, mapSolarSystems.solarSystemName, mapSolarSystems.security
FROM destruction_data
JOIN invTypes
ON (destruction_data.typeID = invTypes.typeID)
JOIN mapSolarSystems
ON (destruction_data.systemID = mapSolarSystems.solarsystemID)
WHERE destruction_data.typeID IN (28850, 28844, 28848, 28846)
ORDER BY destruction_data.date DESC

Results

Out of 975 Jump Freighter kills covering 334 days, there is an average of 20 a week killed. It turns out that you are most likely to get caught in Lowsec in a Rhea.

2013-12-01_jf_kills_by_sec

2013-12-01_jf_kills_by_type

When we look at kills by system, Purjola (0.5), a Highsec system in the Forge stands out as the system with the most losses at 54. Not surprisingly the Lowsec system of Sagain (0.4) comes in second, most likely due to the terrible kickout station that I have covered here.

2013-12-01_jf_kills_by_system

 

More coming soon as I start to think of what types of statistics and trends I can pull out of the data. If you have something you would like me to look at, please leave a comment or tweet @K162space.


California Dreams

IMG_20130725_212504IMG_20131018_142454

It has been a while since I have posted and that is because I have relocated from the US Midwest to California to pursue my dream of working as an engineer in the telecom industry.

My desktop hasn’t been moved because I haven’t found a permanent apartment to call home yet. I’ve only been able to update skill training with an old laptop that can barely run the client. Once things fall into place, I’ll get back into the swing of things.

IMG_20131012_155114 IMG_20131018_150508


New Chapter

No, I am not leaving Eve. I have accepted an Engineering job in the San Francisco Bay Area and will be moving at the end of the summer. This is a major career advancement where I am going from a generalist to an Engineering specialist. My posting will become erratic, but I will return after I get the family settled from the cross-country move.

emot-toot.gif_thumb


Wallet Manager Code Update

It is with great pain that I have to announce that my wallet manager code was compromised at an unknown time in the past. I haven’t spent too much time doing computer forensics because I believe that I was compromised on a previous VM that hosted my site in 2011, which has since been deleted in favor of a OS refresh.

Details about the compromise can be found on this stackoverflow.com post. If you have downloaded and are running a copy of my Wallet Manager, you will want to look at files in the /protected/models/ directory for the exploit code.

Going forward I am going to publish the Wallet Manager code to a public GitHub repository. My goal will be to secure the code, make it open source, and enable community contributions.


Odyssey Dreadnought Blueprint Change

As part of CCP Fozzie’s ship rebalancing efforts, he is removing the ideology of split-weapon systems. Ships like the Typhoon, Phoenix, and Naglfar, which historically had two weapon systems, are being phased out in favor of a single weapon type.

The change for the Phoenix and Naglfar were noted in the Odyssey patches notes as no longer requiring Capital Components which went into construction of the second weapon group.

The Phoenix no longer requires Capital Turret Hardpoints in its construction.
The Naglfar no longer requires Capital Launcher Hardpoints in its construction.
Odyssey Patch Notes

My interperation of these notes was that the build requirements were being removed. Today however, I found that they have shifted to the primary weapon group.

[edit]

I did not see the post in S&I detailing the shift of build requirements per Fozzie.

2013-06-04_twitter_1

 

2013-06-04_dread_changes

Here’s a screenshot of the Naglfar Blueprint post-Odyssey for verification. As always, adjust your build sheets and database tables.

2013-06-01_nag