In-Development TradeDangerous: power-user trade optimizer

@kfsone, I'm back, sort of. Have not had time for much of anything the last couple of months other than an hour or so a night of exploration, and came back to civilization this weekend. My grand plans to submit all the newly discovered stars from my 5,000+ Ly trip came to naught, when I got back and realized that the various ED updates had turned verbose logging off, and I forgot to turn it back on. Arrrgh! Should be able to submit some from my XML before that happened at least eventually.

For what it's worth, hope to resurrect the Jython Swing UI from the dead soonish, family emergencies and ongoing work crises permitting, but progress will likely be slow for the next couple of months at least. Spent today getting source back up to date and trying to remember where I was and how Git and SourceTree worked again, reading back through the forum to see how things were going and taking a quick look at what WombatFromHell has been doing, and the other UI screenshots floating around as well. Have not read through his thread yet or looked at his source but plan to do that at some point as well.
 
I'm trying to add a bunch of prices by making my own .prices files from data outside of eddn.

It seems to work ok if I'm adding stations that are buying stock, but it does not seem to update if I'm adding an item that is for sale.

For example my .prices file would look like :

@ BD+23 2640/Wagner Dock
+ Minerals
Beryllium 0 8164 ? - 2015-04-13 19:31:43

(I'm not worrying about demand/stock and sell price at the moment)

But it does not seem to update and if I try >trade.py update BD+232640/Wag in the popup window Beryllium does not appear at all.

Any ideas?

When you update it only shows the existing items in your .prices by default. Use the -A switch to show all items and if you make any of the prices non-zero then it will add that price.
 
Did you note them? May be we should calculate if the difference is static by having a bunch of test stations.
Even then it would mean having the reputation passed in other tools and specially to EDDN.

CMDR Ibizan said:
Can you recall the differences in price per ton of any commodity?

clavain said:
Are you sure it was reputation, and not different size cargoes?

Unfortunately I didn't note the prices - it was difficult at the time as the implications didn't interest my wingmen and we were in the middle of things. My best recollection was that I was getting ~1380 profit and another wingman was only getting ~1050 profit - the other was inbetween. I was in a type 9 and the lowest profit was in a cobra so if cargo size is also a factor then that would mean that my profit was nerfed a bit and the gap should have been even bigger. So I'm pretty sure that reputation/faction status is the major factor. Further, if cargo size is a factor, then does that only affect the sell price for that one item or does it affect all buy/sell prices?

To check/measure/investigate the nature of this issue will require some coordination I think. Probably best done in a wing simultaneously. AND as @clavain has pointed out that cargo size may be a factor - then buying the same amount of cargo also would seem necessary.
 
Unfortunately I didn't note the prices - it was difficult at the time as the implications didn't interest my wingmen and we were in the middle of things. My best recollection was that I was getting ~1380 profit and another wingman was only getting ~1050 profit - the other was inbetween. I was in a type 9 and the lowest profit was in a cobra so if cargo size is also a factor then that would mean that my profit was nerfed a bit and the gap should have been even bigger. So I'm pretty sure that reputation/faction status is the major factor. Further, if cargo size is a factor, then does that only affect the sell price for that one item or does it affect all buy/sell prices?

To check/measure/investigate the nature of this issue will require some coordination I think. Probably best done in a wing simultaneously. AND as @clavain has pointed out that cargo size may be a factor - then buying the same amount of cargo also would seem necessary.

Part of the reason they added the dividend system is that if a group of people turn up and sell cargo, the prices change as each of you unloads.

But what you were seeing in terms of prices on-screen was a further result of that. Probably needs more research, though.
 
I'm trying to add a bunch of prices by making my own .prices files from data outside of eddn.

It seems to work ok if I'm adding stations that are buying stock, but it does not seem to update if I'm adding an item that is for sale.

For example my .prices file would look like :

@ BD+23 2640/Wagner Dock
+ Minerals
Beryllium 0 8164 ? - 2015-04-13 19:31:43

(I'm not worrying about demand/stock and sell price at the moment)

But it does not seem to update and if I try >trade.py update BD+232640/Wag in the popup window Beryllium does not appear at all.

Any ideas?

a. The "+" lines aren't required if you're feeding TD; it puts them there for human readability but it otherwise ignores them.

b. The line you've supplied specifically says that Beryllium is not in stock here.

Price lines have 6 fields:

Code:
<Name> <stn-paying> <stn-asking> <demand units+level> <stock units+level> <timestamp>

TD doesn't particularly trust it when you tell it that someone is selling an item but not buying it, because that's never true.

But the main problem is the "-". The "demand units+level" field is a pattern as follows:

Code:
?
    Unknown (units = -1, level = -1)

-  or  0
    Unavailable (units = 0, level = 0)
    Supply(units=0, level=0)

123?
    Known units, unknown level  (units = 123, level = -1)

123L
    123 units low (units = 123, level = 1)

123M
    123 units med (units = 123, level = 2)

123H
    123 units high (units = 123, level = 3)

By writing "? -" as the demand and stock values you've said "some unknown demand quantity, and absolutely not for sale". It doesn't matter that you provided a price, there was no stock available. In earlier versions of TD it was represented with "n/a".

What you might want to to TD is:

Code:
 Beryllium 0 8164 ? ? 2015-04-13 19:31:43

But you could also save yourself some hassle by writing one of either:

Code:
 Beryllium 0 8164 ? ? now

or

 Beryllium 0 8164 ? ?

or just

 Beryllium 0 8164

But you shouldn't count on TD accepting an item with only a sale price.

Note that these are peculiarities of how TD imports "local" .prices files, i.e. ones it thinks you are hand editing.
 
Last edited:
Thanks! That seemed to work. Apart from stations that dont exist (I'm adding in data from Thrudds via an excel macro so there's stations there that are not in your data).. eg :

Code:
@ Wolf 1453/Godel Terminal
Indium 0 5756 ? 505839M 2015-04-12 09:56:01

I Get :

Code:
D:\TradeDangerous2>trade.py import cimport.prices
D:\TradeDangerous2\trade.py: cimport.prices:1 ERROR Unrecognized STAR/Station: "
WOLF 1453/GODEL TERMINAL"


D:\TradeDangerous2>trade.py import cimport.prices -i
NOTE: Added local station placeholder for WOLF 1453/GODEL TERMINAL (#16871)
NOTE: Placeholder stations are added to the local DB only (not the .CSV).
NOTE: Use 'trade.py export --table Station' if you /need/ to persist them.
NOTE: Import complete: 1 new items (0 buy, 1 sell) for 1 stations in 1 systems


D:\TradeDangerous2>trade.py market --selling Wolf1453/Godel
Item   Selling   Supply
-----------------------
Indium


D:\TradeDangerous2>

It seems to be saying that its added the station for me but it's not adding the price?

I tried running
Code:
trade.py export --table Station'
and then re-running the import but it's got really confused now Edit : Typo as per the next post. However it still does not add in the prices.

Code:
D:\TradeDangerous2>trade market --selling Wolf1454/God
D:\TradeDangerous2\trade.py: ERROR: Unrecognized origin station: Wolf1454/God
 
Last edited:
D:\TradeDangerous2>trade.py market --selling Wolf1453/Godel

then

D:\TradeDangerous2>trade market --selling Wolf1454/God

I call typo

Well spotted that man.. Will edit to show that.. However it still does not update the price in my local db.

Code:
D:\TradeDangerous2>trade market --selling Wolf1453/God
Item   Selling   Supply
-----------------------
Indium
 
... So I'm pretty sure that reputation/faction status is the major factor. Further, if cargo size is a factor, then does that only affect the sell price for that one item or does it affect all buy/sell prices?

To check/measure/investigate the nature of this issue will require some coordination I think. Probably best done in a wing simultaneously. AND as @clavain has pointed out that cargo size may be a factor - then buying the same amount of cargo also would seem necessary.

Some people have already done this for cargo size - see this thread here a page or two in, and the one linked off it. Not sure if there has ever been an official FD explanation other than that it exists (except when trading at Founder's World). There may be something in the DDA/DDF somewhere, but whether that reflects what is actually happening is anyone's guess.

Edit: The test percentages mentioned here in that thread may not even be constant - it is possible it gets tweaked with every patch or every time they play with the background sim or economy.
 
Last edited:
D:\TradeDangerous2>trade.py market --selling Wolf1453/Godel
Item Selling Supply
-----------------------
Indium


D:\TradeDangerous2>
[/CODE]

Again, TD doesn't quite believe you about this item, and obviously there are some issues with presentation that come up as a result. But the core of the problem is that TD knows that no station ever only sells an item, they ALWAYS offer to buy it back at a loss.

Code:
(.venv)(master)osmith@osmith-mbp:trade$ ./trade.py buildcache -fiq
(.venv)(master)osmith@osmith-mbp:trade$ (echo "@ SOL/TESTING Place" ; echo "Indium 0 1234 ? 1234M now") >test.prices ; ./trade.py import -i test.prices
NOTE: Added local station placeholder for SOL/TESTING PLACE (#16905)
NOTE: Placeholder stations are added to the local DB only (not the .CSV).
NOTE: Use 'trade.py export --table Station' if you /need/ to persist them.
NOTE: Import complete: 1 new items (0 buy, 1 sell) for 1 stations in 1 systems
(.venv)(master)osmith@osmith-mbp:trade$ grep -C3 SOL/Testing data/TradeDangerous.prices
      Reactive Armour            1866    1889          ?     3598M  2015-02-16 20:43:44


@ SOL/Testing Place
   + Metals
      Indium                        0    1234          ?     1234M  2015-04-15 00:12:57
(.venv)(master)osmith@osmith-mbp:trade$ ./trade.py market -v sol/testing
    Item    Buying     Avg Age/Days Selling     Avg Supply Age/Days
-------------------------------------------------------------------
+METALS
    Indium                                                         
(.venv)(master)osmith@osmith-mbp:trade$ (echo "@ SOL/TESTING Place" ; echo "Indium 1230 1234 ? 1234M now") >test.prices ; ./trade.py import -i test.prices
NOTE: Import complete: 1 updated items (1 buy, 1 sell) for 1 stations in 1 systems
(.venv)(master)osmith@osmith-mbp:trade$ grep -C3 SOL/Testing data/TradeDangerous.prices
      Reactive Armour            1866    1889          ?     3598M  2015-02-16 20:43:44


@ SOL/Testing Place
   + Metals
      Indium                     1230    1234          ?     1234M  2015-04-15 00:13:40
(.venv)(master)osmith@osmith-mbp:trade$ ./trade.py market -v sol/testing
    Item    Buying     Avg Age/Days Selling     Avg Supply Age/Days
-------------------------------------------------------------------
+METALS
    Indium   1,230   5,974     0.00   1,234   5,684 1,234M     0.00

I'll try and look into why it doesn't give you better feedback, and/or add some logging to the -ww output, and look at why we're seeing blank output - I suspect that I'm adding the StationItem line regardless of whether I'm going to add a Buy or Sell line, and see if I can clean those up, but as I said before, the fix fix for your issue is to supply a station buying price.
 
Last edited:
Again, TD doesn't quite believe you about this item, and obviously there are some issues with presentation that come up as a result. But the core of the problem is that TD knows that no station ever only sells an item, they ALWAYS offer to buy it back at a loss.

Code:
(.venv)(master)osmith@osmith-mbp:trade$ ./trade.py buildcache -fiq
(.venv)(master)osmith@osmith-mbp:trade$ (echo "@ SOL/TESTING Place" ; echo "Indium 0 1234 ? 1234M now") >test.prices ; ./trade.py import -i test.prices
NOTE: Added local station placeholder for SOL/TESTING PLACE (#16905)
NOTE: Placeholder stations are added to the local DB only (not the .CSV).
NOTE: Use 'trade.py export --table Station' if you /need/ to persist them.
NOTE: Import complete: 1 new items (0 buy, 1 sell) for 1 stations in 1 systems
(.venv)(master)osmith@osmith-mbp:trade$ grep -C3 SOL/Testing data/TradeDangerous.prices
      Reactive Armour            1866    1889          ?     3598M  2015-02-16 20:43:44


@ SOL/Testing Place
   + Metals
      Indium                        0    1234          ?     1234M  2015-04-15 00:12:57
(.venv)(master)osmith@osmith-mbp:trade$ ./trade.py market -v sol/testing
    Item    Buying     Avg Age/Days Selling     Avg Supply Age/Days
-------------------------------------------------------------------
+METALS
    Indium                                                         
(.venv)(master)osmith@osmith-mbp:trade$ (echo "@ SOL/TESTING Place" ; echo "Indium 1230 1234 ? 1234M now") >test.prices ; ./trade.py import -i test.prices
NOTE: Import complete: 1 updated items (1 buy, 1 sell) for 1 stations in 1 systems
(.venv)(master)osmith@osmith-mbp:trade$ grep -C3 SOL/Testing data/TradeDangerous.prices
      Reactive Armour            1866    1889          ?     3598M  2015-02-16 20:43:44


@ SOL/Testing Place
   + Metals
      Indium                     1230    1234          ?     1234M  2015-04-15 00:13:40
(.venv)(master)osmith@osmith-mbp:trade$ ./trade.py market -v sol/testing
    Item    Buying     Avg Age/Days Selling     Avg Supply Age/Days
-------------------------------------------------------------------
+METALS
    Indium   1,230   5,974     0.00   1,234   5,684 1,234M     0.00

I'll try and look into why it doesn't give you better feedback, and/or add some logging to the -ww output, and look at why we're seeing blank output - I suspect that I'm adding the StationItem line regardless of whether I'm going to add a Buy or Sell line, and see if I can clean those up, but as I said before, the fix fix for your issue is to supply a station buying price.

Ahh that works, Ok I'll add a fixed 5% lower price for those and that works.

Next question(s).

1). If you dont specify to/from or just specify --loop in run does it actually iterate through every possibility to give you the best possible loop?

2). If you specify hops is it possible for force it to find routes that have that many hops and to remove these types of ping/pong results? (Alternatively you put in 3 hops and only get two hop results). Really looking for loops with unique (apart from the last hop) results. But I cant use unique with loop or to/from with unique )

Code:
D:\TradeDangerous2>trade run --routes 5 --pad-size L --capacity 1 --credits 1000
000 --ly-per 20.4 --jumps-per 1 --loop --hop 7
NOTE: Pruned 7 origins too far from any end stations
NOTE: Pruned 609 origins too far from any end stations
NOTE: Pruned 2511 origins too far from any end stations

HIP 15614/Hevelius Hub -> HIP 15614/Hevelius Hub
  HIP 15614/Hevelius Hub: 1 x Palladium,
  TUBALITH/Winthrop Vision: 1 x Imperial Slaves,
  HIP 15614/Hevelius Hub: 1 x Palladium,
  TUBALITH/Winthrop Vision: 1 x Imperial Slaves,
  HIP 15614/Hevelius Hub +5,992cr

TUBALITH/Winthrop Vision -> TUBALITH/Winthrop Vision
  TUBALITH/Winthrop Vision: 1 x Imperial Slaves,
  HIP 15614/Hevelius Hub: 1 x Palladium,
  TUBALITH/Winthrop Vision: 1 x Imperial Slaves,
  HIP 15614/Hevelius Hub: 1 x Palladium,
  TUBALITH/Winthrop Vision +5,992cr

HIP 15614/Hevelius Hub -> HIP 15614/Hevelius Hub
  HIP 15614/Hevelius Hub: 1 x Palladium,
  TUBALITH/Winthrop Vision: 1 x Imperial Slaves,
  HIP 15614/Hevelius Hub: 1 x Palladium,
  TUBALITH/Winthrop Vision: 1 x Imperial Slaves,
  HIP 15614/Hevelius Hub: 1 x Palladium,
  TUBALITH/Winthrop Vision: 1 x Imperial Slaves,
  HIP 15614/Hevelius Hub +8,988cr

Cheers!
Dastardly
 
Ahh that works, Ok I'll add a fixed 5% lower price for those and that works.

Next question(s).

1). If you dont specify to/from or just specify --loop in run does it actually iterate through every possibility to give you the best possible loop?

More or less, the less being that when it's in loop mode it can set distance limits and so it can look at less candidates, so it becomes a lot faster than running without --loop.

What it actually does, though, is as it goes through it remembers all the routes that looped (start == end) regardless of how many hops, and then it divides score/hops to level the playing field. I'm not sure how fair this is, since it always seems to favor short loops. I know people think that a<->b grinds are the most efficient, but it's even less likely when they're stable.

2). If you specify hops is it possible for force it to find routes that have that many hops and to remove these types of ping/pong results? (Alternatively you put in 3 hops and only get two hop results). Really looking for loops with unique (apart from the last hop) results. But I cant use unique with loop or to/from with unique )

Interesting, I hadn't thought of that. That sounds like a valid use of --unique. Put in a ticket on the issue tracker (http://kfs.org/td/issues) and if nobody else jumps the gun I'll take a look at the weekend.
 
I posted a little while back about places that had really old data, a recap of the 20 oldest station data samples:

Code:
$ trade.py old --limit 20 -vvv
Station                           Age/days      StnLs Pad
---------------------------------------------------------
V401 HYDRAE/Swanwick Terminal       122.79      3.84K Med
COSI/Marshall Hub                   121.13        13K Med
G 180-18/Bamford Terminal           120.60      1.82K Med
MAGEC/Arrhenius Colony              120.60         16 Med
MOMBALUMA/Hughes-Fulford Terminal   120.08        539 Lrg
UOLUSKAS/Moisuc Dock                119.88        429 Lrg
BELALANS/Shoemaker City             119.88         78 Lrg
OVIMBAIA/Morris City                119.40        106 Lrg
HIP 84255/Land Port                 119.24      1.93K Lrg
PARAUDIKA/Mouhot Port               118.89         31 Med
SHAKAPA/Gibson Dock                 118.86      1.86K Med
TIMOCANI/Pennington Terminal        118.83          ?   ?
11 CEPHEI/Cook Gateway              118.82        844 Lrg
AKNANGO/Pinto Hub                   118.81        325 Lrg
AKNANGO/Skolem Landing              118.80        464 Med
SHOTEP/Walters Refinery             118.67          ? Med
HIP 85010/Volynov Platform          118.46          ?   ?
CHACOBOG/Trinh Enterprise           118.32          ?   ?
JARILDEKALD/Elvstrom Platform       118.31          ?   ?
JARILDEKALD/Reed Stop               118.30          ?   ?

So we now have some 4-month old data in there :) But you'll also see the list is different. In some of the few occasions I've had chance to get in-game, I've gone visiting.

What I found was interesting.

Firstly, at many of the stations, the prices - even the quantities - appeared to be "fosilized" - they were exactly as they had been 90-100 days ago. At none of them was I ever able to acquire a mission, and I couldn't help but wonder if that was a faction, because the mission system does affect the economy of a system. If nobody has been able to do missions at these stations ...

But secondly, there was great money to be made, which people are missing because of --age.

Because of the number of players anticipating A<->B routes to be profitable, our highest concentration of maintained data is between systems that have mediocre quasi-stable turnovers; it looks like players think 1000-1200kcr/ton is "good" is good. Some of the most trafficed areas have one hop that's 1500-1600cr/ton and the other is 900cr/ton. While I hate to introduce math, one hop of 900 and one hop of 1600 means an average of 1250cr/ton. If you sold 1 ton each way, you'd gain 2500 cr, if both hops made you 1250 cr you'd be making the same profit...

Next door there's a route which makes 1190, 1310 and 1430cr a hop? That's got to make you less money right? I mean, you were making 1600cr/ton a minute ago with only two stops? Except this route is making 1310cr per ton.

Lets say you carry 100 tons along both routes:

A -> B + 900,000 -> A + 1,600,000 -> B + 900,000 => just under 3.4mil cr

C -> D + 1,190,000 -> E + 1,310,000 -> F + 1,430,000 => 3.93 mil cr.

What appears to happen is that players occasionally see a really good single-hop profit, something going for 1750cr/ton gain, and immediately set about finding an A<->B loop and find something that's 1750/1100. When they get there, it turns out the 1750 is now 1700 and the 1100 turns out to be 10x0. They do a couple of runs and they only seem to be making like 1300cr/ton which is barely better than what they had, and naturally you feel disinclined to waste time skipping between pools.

ED has an economy so focusing on A<->B loops like this is generally a lose-lose situation for you unless you're willing to also participate in the mission/combat portion of the game to drive the demand for the commodities you want to trade.

My intent here isn't to scald anyone for "doing it wrong", but to explain some of the mechanics as I see them, because I'm sure some of you are tiring of the grind, and I thought it worth weighing in; TD has options that will let you back yourself into a grindy corner because of limitations of the data we have. Whether it's checking for nearby stations we don't have data for or old station data and using the "trade" command.

Another useful thing to do - occasionally - "--limit". If you've got 500 cargo capacity, try using "--limit 450" sometimes and let TD suggest some extra stuff to help you stir up sales a bit.
 
Good info.

I used to use --age, but then was told single commodity which haven't been updated in a while (like some leftover as fdev changed some economy stuff) can drag whole stations age status down. Or did I misunderstood this?

When looking at TD results I never focus on single profit per ton, I always keep a standard set of jumps/hops and then look the complete profit and if that is good, I look in more detail each hop and check that in there is no oddities in the route. Although have to admit, often times its just race to keep squeezing out more and more profit with TD before embarking into any route heh.
 
Good info.

I used to use --age, but then was told single commodity which haven't been updated in a while (like some leftover as fdev changed some economy stuff) can drag whole stations age status down. Or did I misunderstood this?

It comes down to this: The OCR tools provide incomplete data, so we had to break the import model to support them. Along with people who contribute by submitting individual line-item updates, the data set as a whole acquires certain properties. The data we have for most stations is "gossip", we have a particular snapshot value from a point in time and no way to tell what the lack of updates means.

This results in spreads of prices at stations, and TD's still a little inconsistent about how it represents this. In particular, sometimes a station will wind up with a single line item that's ancient because the only people who have visited the station in a while are using an OCR tool, and the OCR tools don't know whether the item is gone or you didn't take a screenshot of them, so the OCR tools only send updates, not deletes...

The station then gets a bad rep for having "old" data, and people avoid it, missing out on great prices.

When looking at TD results I never focus on single profit per ton, I always keep a standard set of jumps/hops and then look the complete profit and if that is good, I look in more detail each hop and check that in there is no oddities in the route. Although have to admit, often times its just race to keep squeezing out more and more profit with TD before embarking into any route heh.

If I'm doing just *one* hop, I always ask TD for 3. If you ask for a single-hop, TD is looking for one thing: something to buy here and sell there for the absolute top dollar. That's it. It's not even going to check whether that destination has anything to sell.

So asking for 1-hop destinations as a way of route planning (that is: trade.py run --from X --hops 1 vs --from X --hops 1 --to Y or trade.py trade X Y) may get you a nice 1750cr/ton hop but then you invariably wind up doing less than 800cr/ton to try and get back into a good run.

-----------

I've just landed 1.8.2 which adds "--loop-int", this lets you specify that you don't want to go back to the same station in less than X hops, e.g.

Code:
trade.py run synteini/lager --pad L --hops 6 --sum --ls-max 4000 --stock 10000 --ly=42 -li=2

will find routes that requires at least 2 hops between returns to a given station

A->B->A->B <- not allowed
A->B->C->A <- allowed
 
I've just landed 1.8.2 which adds "--loop-int", this lets you specify that you don't want to go back to the same station in less than X hops, e.g.

Code:
trade.py run synteini/lager --pad L --hops 6 --sum --ls-max 4000 --stock 10000 --ly=42 -li=2

will find routes that requires at least 2 hops between returns to a given station

A->B->A->B <- not allowed
A->B->C->A <- allowed

[Request] --loop-sys, could we also have a loop that will avoid going back to the same system completely for those systems that have more than one station?

[EDIT] or --unique-sys
 
Last edited:
Just to be clear what I mean is that I use 2 jumps, 2 hops which comes from TD as default or if I feel adventurous I make it 2 jumps and heh 13 hops, thirteen is the magic number as it just nicely fits on linux shell screen size :)

But yeah my usual benchmark is the TD default two and two. Its then easy to check the final lump sum of profit if its worth it or not, no need to tinker with individual per ton profits etc.
 
Im not well versed in the cmd prompt but i seem to be having a small problem. I have python working and when I put the command trade.py in the general help page with the subcommands is displayed but whenever i put in a subcommand after trade.py it just shows the general help page again. What am i doing wrong?
 
I've just landed 1.8.2 which adds "--loop-int"...

Ah - very cool. I love that. I have been generating a loop with hop # based on how long I estimate I want to trade for and based from the station where my type 9 was parked. But often I would be sent back to the start too early. This makes things much more interesting. Excellent.
 
Im not well versed in the cmd prompt but i seem to be having a small problem. I have python working and when I put the command trade.py in the general help page with the subcommands is displayed but whenever i put in a subcommand after trade.py it just shows the general help page again. What am i doing wrong?

Can you copy & paste what you're doing (press alt+space if you're in windows to get the command window) or take a screenshot?

If you have Python installed "for all users" then you should be able to type:

Code:
[i]C:\...> [/i] [b]trade.py[/b]

and get something other than "command not found" :) If that's the case, you should next be able to type

Code:
[i]C:\...> [/i] [b]trade.py local sol --ly 6 -vv[/b]

and get some info about systems near sol.

You probably then want to import some data, and if you're ok with using "maddavo"s crowd-sourced data (http://www.davek.com.au/td/) you can do that by typing:

Code:
tdimad -O csvs

there are also some "helper" batch files in the "scripts" directories. For more on those, see the wiki or the scripts/README.txt file (just open it in notepad or something).

-Oliver

- - - Updated - - -

Just landed a new update with ~300 new systems and "--shorten" argument to "run" command.

--shorten requires "--to"; it does the same thing that "--to" does, but it will allow routes that reach the destination in less than --hops jumps to be considered and at the end of the route calculations it will compare routes based on their average Gain Per Ton (gpt).

This will get stuck on loops if there's a really good loop between you and your destination (I just had this happen on the way to Shinrarta, someone had input a really bad price for Gold that produced >3000cr/ton profits, I shoulda used --max-gpt, duh).

-Oliver
 
Back
Top Bottom