Pilot Archive

---

Raja_Asenn wrote:

I've added the requested Red Skull and TIE duties. It will be useful if you guys can let me know what squadrons those duties are attached to.

Also, previously it was requested that I add T4 black sun duties for RSF and Havok - I've done so, but it'd be useful to note which systems those missions actually occur in.

---

§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§
§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§
§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§
§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§
§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§
X Machine'Zed X
Obsidian Dagger Squadron

Thanks for the info guys.

And thanks to Johro and Estep for adding loot sessions last night. I now no longer think that I wasted my time in writing this thing, heh.

Even the preliminary data we've got so far is really interesting. Look at the discrepancy in loots per minute between the mercenary freighters and the Black Sun duties - the freighter spawn yields components almost five times as fast. That's just bonkers.

---

SimplyADreamer wrote:

Please add the pirate destroy duty mission of the Dant neutral space station. Gonna submit my logs then. It's tier2-3.

---

---

denedes wrote:
As I found out, yield from Mercenary Freighters is limited by the amount of DPS you bring... 2 crafted L9 blasters with WO3 won't cut it.

I won't be going back there until I get my L10 and L8 guns REd... just need a couple more pieces to make them perfect

---

That's a real good point Denedes. I'm thinking about doing something crazy to link the Lootalyzer to the Ship Registry, so that we can display some kind of modified aggregate efficiency statistic that incorporates combined weapon DPS. It'll be down the road a bit.

Also, props to Denedes for being far and away the number one Lootalyzer contributor. He's got almost as much analysis-time in six sessions as all other contributors combined do in seventeen. The application wouldn't even be off the ground yet if not for his contributions.

---

rabblerowser wrote:

Still agape in appreciation of the added enjoyment of trying to analyze the spawns. Hate to mix hard numbers with hearsay, but if there is any possibilty of including day-of-the-week in analysis tools - rumor has it that Sundays are more generous, others have said loot may be related to player density, or maybe system resets, or...well you get the idea..there's every flavor of rumor in the world floating around.

/deepbow

---

Hmm...mixed feelings about saying anything, but bottom line it's your call and I wanna get your opinion:

Data Integrity: Have noticed that the total kills in T-4 Blacksun (RSF Duty) is diverging from opitimum. The mission spawns 85 kills (hehe...your site taught me that, as I woulda never done the math myself)...13 missions completed at the moment should be 1105 kills, meaning 14 stray data points. Don't know what offers the best return on investment and understand the desire to encourage participation. So, what are your thoughts?

Also, am curious how much of a statistician you may be; with this many variables have you determined the minimum sample size to get relatively accurate loot level/type distribution rates? Everytime I submit a log, I look at the numbers, take a swig of my favorite beverage and think...aha...so that is how they have it set up....

Thanks again for your site...

---

rabblerowser wrote:

Also, am curious how much of a statistician you may be; with this many variables have you determined the minimum sample size to get relatively accurate loot level/type distribution rates?

---

My last math class was algebra 2, my senior year of high school, and I failed that. Which is to say, I'm not much of a statistician. My thought so far has been to wait until we've got an arbitrarily vast amount of data and then do 'something fancier' with it. Deep, huh?

If you've got ideas, I'm all ears. I can code most anything, if you give me good rules to follow.

Upon further review...the lootalyzer is missing some loots. I think the problem is that it's failing to match the signature from the log file with the class name it matches in the database. This appears to be happening in about 8% of cases.

I'm going to write a safety net that will 'catch' missed loots and throw them into a bucket where I can input them manually and update the signature match routine so it won't miss that class again.

But...there's all that bad data. Bad data gives me a rash. I really, really hate to toss out people's loot sessions, especially since it's a bug in my code that's invalidating the data...but...that's what I'm gonna do. Sorry folks. If the app wasn't still in its infancy I'd consider hanging onto it.

Some stuff will be preserved. At a glance it looks like I have the source files for 10 sessions....about a quarter of the total sessions that have been submitted. With the momentum the app has picked up recently, we should replace the purged information within a couple of days.