Ships & Modules

Project news: (updated 01-26-2016)

At the moment, I am the only one maintaining pyfa. As some folks know, Kadesh has decided to leave the EVE Universe due to :stuff: and no longer has interest in maintaining pyfa or it's related projects. I have been with the project and headed development of it for a little over two years now, so it's been handed over to me. As such, the pyfa repository and all related repos has been moved to a GitHub Organization called 'pyfa-org'.

I am in need of someone who is familiar with: OS X general development and architecture (and keeps up with releases and what they might break), Python, and py freezing applications. There have been many pitfalls while moving to support wxPython 3.0 on OS X: I had to update the binaries, and fell into many traps due to my general lack of knowledge when it comes to OS X development. For example, building the binaries must be done on 10.7 - if I build them on my 10.10 Hackintosh, we have folks on earlier versions who cannot launch pyfa. At the moment, though, pyfa runs pretty well on 10.7-10.10, but certain versions still have certain issues. If you would like to help tackle these problems, contact me.

For the past few years, you may have heard of a new engine being written for pyfa that would perform fitting calculations faster and allow us to update much more quickly. I'll give a brief update to that: Kadesh was the main person behind that project, and while there is a lot done on it, it is not completed. Unfortunately, I am not versed in it's internal workings to feel comfortable developing on it yet, and so this project is on the backburner indefinitely until I can familiarize myself with it a bit more. This is also hampered by the fact that pyfa requires a complete rewrite to utilize it, which is a daunting task for someone who is both a fulltime student and employee. This does not, however, affect the current codebase of pyfa, which is still regularly updated and improved upon. If anyone is interested in helping with development of the new engine, it is still found under Kadesh's GitHub account: https://github.com/DarkFenX/Eos

Not sure if this has been brought up in the past or not, but would it be possible to add a (rough) estimator for enemy lock times based on your fits sig radius? I'm aware that this will vary widely based on enemy skills/fits etc, but even if an estimator could be based off of ship class similar to the current lock estimator, avoiding skills entirely. This will definitely help anyone looking to build quick warp fits, etc. Also, keep up the good work! Cheers!

Mmmmh, i try to fetch my skills, but i get an error, called: The read operation timed out.

Any solutions about this? i dont know if my firewall is blocking it...

thx in advance.

Annoying wx bug/glitch, everytime a (any or none really) fit is updated the right side information gets all messed up. Eventually its unusable.

http://giphy.com/gifs/YIpohwxkZaous/html5
http://i.imgur.com/4E9lw08.png

Python: 2.7.10
wxPython: 3.0.2.0
SQLAlchemy: 1.0.11

Most likely a problem with your firewall or something similar. That error usually happens when it can't connect to the server. Try EVEMon or something else that fetches the skills and see if it works or not. If not, then it's definitely something in your network environment

hello, i'm a new user switching from eft and i'm wondering if pyfa has the tooltip like in eft to view ship bonuses?

since the new structures will behave fittings wise similar to ships, i am wondering if you are planning to add them too for pyfa once they are out?

Nope. There was effort a few years ago to port pyfa to some sort of web interface, but that was abandoned when the other developers left the team. Besides, o.smium manages to browser-based fitting quite well



Maybe. We'll see =)



We'll have to see. It all depends on how the stuff works on the back end. Might have to take a bit of reworking the available market code and whatnot, but as long as they are similar enough to fits, it should be workable. There's also the question of if it's really even wanted (will the stations have cap / dps / etc). Depending on the info needed, we may have to develop some sort of system for changing the stats info depending on the context (fit vs station).

If it happens, most likely won't see it in pyfa until a few months after citadels release, however, due to time constraints



1) What is the need to see all of your ships at once? If it' simply to review old fits, it might be possible to display ships based on last modification. We don't currently track this (the timestamp given is the time it was created IIRC). Maybe search criteria such as time>2015 or something. But even this (smart search criteria) would be a rather significant undertaking.

2) This has been requested before: https://github.com/pyfa-org/Pyfa/issues/172 However, it's not as easy as it may seem due to the way pyfa handles the market. I haven't looked at this issue in a long time, and can't remember the specifics. It's on the list until it isn't anymore. =)

It is a quality of life situation that enables you to either prune old fittings out so that you can start fresh, review fittings etc.


Heck a partial implementation where it just lists each saved fit, (sort by name or shiptype/hullname) one after the other would satisfy the need for managing and pruning fits. Anything else would be gravy.

I was actually just Googling how to do this. Nice coincidence that it is the latest discussion! I had noticed that all my fits were listed in the ship window after doing an XML import and was thinking it was a new feature.

Basically, next to the hide empty ship groups should just be a button that displays all fits. I started looking around in your code and edited the following code locally:

def OnScheduleSearch(self, event):
search = self.BrowserSearchBox.GetValue()
# Make sure we do not count wildcard as search symbol
realsearch = search.replace("*", "*")
if len(realsearch) >= 1:
self.lastSearch = search
wx.PostEvent(self.shipBrowser,SearchSelected(text=search, back = False))

The wildcard works after this change (asterisk not deleted and length >=1), but in addition to showing all of my fits, it also shows all ships as well. I may try to dig more into the code to figure out how to hide all ships while searching using a wildcard.

Edit:

Did some more code browsing, and made the following edit to get wildcard search to work for current fits (I also added a sort to the array to display the ships by ship type and name on the wildcard search):

if query != '*':
ships = sMkt.searchShips(query)
fitList = sFit.searchFits(query)

for ship in ships:
self.lpane.AddWidget(ShipItem(self.lpane, ship.ID, (ship.name, len(sFit.getFitsWithShip(ship.ID))), ship.race))

for ID, name, shipID, shipName, booster, timestamp in fitList:
self.lpane.AddWidget(FitItem(self.lpane, ID, (shipName, name, booster, timestamp), shipID))
if len(ships) == 0 and len(fitList) == 0 :
self.lpane.AddWidget(PFStaticText(self.lpane, label = u"No matching results."))
self.lpane.RefreshList(doFocus = False)

if query == '*':
fitList = sFit.searchFits(query)
fitList.sort(key=lambda x:(x[3],x[1]))

for ID, name, shipID, shipName, booster, timestamp in fitList:
self.lpane.AddWidget(FitItem(self.lpane, ID, (shipName, name, booster, timestamp), shipID))
if len(fitList) == 0 :
self.lpane.AddWidget(PFStaticText(self.lpane, label = u"No matching results."))
self.lpane.RefreshList(doFocus = False)