In-Development TradeDangerous: power-user trade optimizer

It would never occur to me to NOT share the pricing data. I've been doing that all along. What I haven't been doing is adding the intermediate stars to EDSC. A big reason for that: you have to spend a few minutes in the stellar map taking distances down, and while you're in the map, you're incredibly vulnerable to NPCs jumping you. I suppose I could wander out a couple hundred LY and drop out of supercruise; an NPC would have to trip across my USS to go after me.

I HAVE been adding the stars, because I was getting lonely and wanted to make it easier to find my part of space.

Regarding the few minutes 'jeopardy' in a new system, I've got this down to around 90 seconds now. I have names of 6 'reference' systems bound to switches SW1->SW6 on my X-55 throttle using the Saitek software. So I am able to rapidly paste them into the web site and the game's galaxy map. :)
 
That'd be awesome.

I collected data for 9 systems; 8 got "Increased CR for..." messages, so those should have gone from CR=1 to CR=2. One of them, though, got the "New system" response... and no coordinates were displayed. Seems like a bug.

No, it means what it says. That was a new system. cr 0. More people need to confirm it for it to reach "calculated".

Minveni said:
Speaking of bugs, but probably in EDSC - when I submitted distances for the 5 standard stars and for one of my own, I had no troubles. When I did the five additional stars (BOB, PEPPER, etc.), I would often get the "hey, those numbers don't work, please confirm data for these stars" hate message. When I re-checked, all the numbers had been correctly entered, but submit-distances.py continued to fight me on it. I got into the habit of simply refusing to enter distances for the additional stars and entering data only for the 5 standards plus one of my own; never got a reject at that point.

It possible you've missed the point. EDSC is a crowd-sourcing project, and as such, it's full of bad, user-entered data, including severe cases of high-cr bad data. If it wasn't, I'd just scrape from it straight into TD and we wouldn't be having this discussion.

When you submit your perfectly correct values to BOB or PEPPER - which are in the list because, duh, they have some really bad data and it's going to take a lot of commanders submitting corrections to convince EDSC they're wrong - EDSC reports that the data you submit doesn't match what it already knows. There's no way I can tell if it's the data you just entered or the data that was already entered.

So I give you a chance to re-enter values for the links EDSC complained about. If you check and re-submit the same distances, it will boost the CR of the data you're giving, and eventually you'll stop getting the warnings.

Unfortunately, some systems - BOB, PEPPER, GAMMA MUSCAE, etc - someone really screwed up. I suspect someone typed in their *target* system rather than *current* system and then entered a lot of distances.

I don't expect anyone to flog a dead horse or make this into work for themselves, but submitting those corrections is actually one of the most important forms of contributing. The positions of BOB and PEPPER that are currently in TD from EDSC are - I think - the wrong ones, pending us getting enough of the right corrections that EDSC recalculates their positions properly.

BOB and PEPPER were in the built-in outliers list for a while to try and get more people correcting them.

Lastly, a note on submit-distances: you can "q" out of any section, so you don't have to use the standard-candle stars at all. You certainly do not have to submit distances for all the stars. 5 is the ideal number you should answer. I should probably make it do that on its own.
 
I HAVE been adding the stars, because I was getting lonely and wanted to make it easier to find my part of space.

Regarding the few minutes 'jeopardy' in a new system, I've got this down to around 90 seconds now. I have names of 6 'reference' systems bound to switches SW1->SW6 on my X-55 throttle using the Saitek software. So I am able to rapidly paste them into the web site and the game's galaxy map. :)

"submit-distances" copies each name it prompts with into the paste buffer - so you only have to paste once when you're using it. Firing off the 5 standard systems should take 30-45s.

Other advantages are the local cache of problem/interesting systems (data/extra-systems.txt; see other users's descriptions of how they use that to track their own additions to give them extra CR boosts without lots of extra work) and prompting for bad distances to the star you're submitting without having to manually copy/paste the names.
 
Thanks for explaining; makes much more sense. I couldn't understand why/how BOB and PEPPER got so screwed up that they'd constantly be causing troubles; totally makes sense, though. I don't know if corrections for those screwed-up systems are one-per-CMDR or one per submission; one might think that a few dozen updates would be enough to drag'em closer to reality, but I guess not.
.
Another night, another 14 stars submitted to EDSC. And 7 stations updated in EDDN. Did some trading, pushed my favorite minor faction with some donations, killed a couple pirate NPCs in my adopted home system... not a bad night's work.
 
Thanks for explaining; makes much more sense. I couldn't understand why/how BOB and PEPPER got so screwed up that they'd constantly be causing troubles; totally makes sense, though. I don't know if corrections for those screwed-up systems are one-per-CMDR or one per submission; one might think that a few dozen updates would be enough to drag'em closer to reality, but I guess not.

I'm not sure with those two, but I don't think it helped when edsc.py was sending "comander" name (one m ;-)
 
Code:
v6.11.0 Feb 21 2015
[FONT=Arial Black][SIZE=2][B]. (kfsone) Added "market" command for viewing station buy/sell list
   e.g. trade.py market ramoncity --buy --sell -vv[/B][/SIZE][/FONT]
. (kfsone) Lots of improvements to edscupdate.py;
   - added --random, checks 10 random new systems,
   - added --conf N for changing the confidence rating,
   - added --detail (-v) and --debug (-w),
   - added --summary
   - added --test (use the EDSC test database),
   - added explanatory "splash" text (--no-splash or -NS to skip),
. (kfsone) Allow a cache rebuild at the start of a mad import
+ (kfsone, maddavo) Lots of Systems and Stations

I'm still adding Systems, I've been flying around to correct a couple of really bad ones including one I'd screwed up (COL 285 SECTOR QE-M B22-6).
 
NOTE: With the update in TradeDangerous today (v6.12.0) the System.csv file format has been changed. Maddavo Market Share is updated to support the new format so if you are having troubles then pls update to the latest version of TD.
 
NOTE: With the update in TradeDangerous today (v6.12.0) the System.csv file format has been changed. Maddavo Market Share is updated to support the new format so if you are having troubles then pls update to the latest version of TD.

Just incase anyone missed the readme update above -- we've added "Market" and "Shipyard" fields to the station table - a station with 'N' in the market column has been visited and confirmed to have NO market.

-Oliver
 
You can see if the station has a commodities market when you look at the station details in the system view. As far as I have seen, only outposts may have no market.
 
I have been to one of the huge space stations that did not have a marked. I found it kind of strange to be honest.
 
Hello,
still i have a problem to get TD work again.
(since new TDversion),and since i installed all from the scratch (new gitclone from bitbucket,new python):
i do some search, but found nothing, so i decided to make a post:
---------------------------------------------------------------------------------------------------------
ERROR: Unable to load the Python 'requests' package.
Do you want me to try and install it with the package manager (y/n)? y
Downloading/unpacking requests
Installing collected packages: requests
Cleaning up...
Exception:
Traceback (most recent call last):
File "C:\Users\Gerhard\SkyDrive\Dokumente\REPOS\tradedangerous\transfers.py", line 16, in <module>
import requests
ImportError: No module named 'requests'


During handling of the above exception, another exception occurred:

...etc
--------------------------------------------------------------------------------------

maybe there is a simple solution,
thanks

 
Last edited:
Station Editing

I have finished a function that may be useful on the Maddavo Market Share site - Station Editing. You can now add, edit, delete stations in a web-interface (it's pretty basic) but it may be easier for some. The Station.csv file is updated within 2 minutes of your changes (usually) - so you can then download your changes using the import/maddavo plugin.

The is a link on the main page in the middle where it says "EDIT STATIONS" OR click here: http://www.davek.com.au/td/editstation.asp .
 
Last edited:
Hello,
still i have a problem to get TD work again.
(since new TDversion),and since i installed all from the scratch (new gitclone from bitbucket,new python):
i do some search, but found nothing, so i decided to make a post:
---------------------------------------------------------------------------------------------------------
ERROR: Unable to load the Python 'requests' package.
Do you want me to try and install it with the package manager (y/n)? y
Downloading/unpacking requests
Installing collected packages: requests
Cleaning up...
Exception:
Traceback (most recent call last):
File "C:\Users\Gerhard\SkyDrive\Dokumente\REPOS\tradedangerous\transfers.py", line 16, in <module>
import requests
ImportError: No module named 'requests'


During handling of the above exception, another exception occurred:

...etc
--------------------------------------------------------------------------------------

maybe there is a simple solution,
thanks


You need to install the 'requests' module by hand. I'm assuming you're using windows, so try the following commands in a Windows command prompt. If these commands fail, you may need to run the command prompt as administrator:

Code:
python -m pip install --upgrade pip setuptools requests

Then try the following:

Code:
python -c "import requests; print('OK')"
 
You need to install the 'requests' module by hand. I'm assuming you're using windows, so try the following commands in a Windows command prompt. If these commands fail, you may need to run the command prompt as administrator:

Code:
python -m pip install --upgrade pip setuptools requests

Then try the following:

Code:
python -c "import requests; print('OK')"

works perfect.
(needed to run as administrator)

thank you very much
 
If I run trade.py shipvendor, how do I get updates to you?

If you're a git user, a push request is preferable,

otherwise one of:
a/ Do trade.py export --tab shipvendor and then git diff dat/ShipVendor.csv or "Actions > Create Diff" in SourceTree,
b/ Do trade.py export --tab shipvendor and then (a) dos: findstr SYSORSTATIONNAME data\ShipVendor.csv, (b) bash: grep STATIONNAME data/ShipVendor.csv
c/ Copy the commands you used to add the ships

then paste the result into the Issue Tracker ticket for gathering data:

https://bitbucket.org/kfsone/tradedangerous/issue/105/collect-distance-black-market-and-pad-size

- - - - - Additional Content Posted / Auto Merge - - - - -

Code:
[b]
v6.12.1 Feb 26 2015
. (kfsone) "buy" command:
  - now accepts multiple arguments (e.g. explosives,clothing),
  - new "--one-stop" (-1) option only shows stations that carry the full list,
  - mixing ships and items is not allowed,
   e.g.
     trade.py buy food clothing fish
     trade.py buy --near achenar fish,food,grain --one-stop
     trade.py buy --near achenar --ly 100 type6,type7 --one-stop
     trade.py buy --near achenar --ly 100 type6,type7 -1
[/b]
 
Code:
[b]
v6.12.2 Feb 26 2015
. (kfsone) "run" command:
  - added "--direct" option:
    - only allows 1 hop,
    - --jumps and --ly-per are ignored entirely,
    - ignores route/distance between stations,
   e.g.
     trade.py run --from achenar --to lave --cap 50 --cr 100000 --direct
[/b]
 
I am having problems with --from and --to switches of trade.py run.
Included my input and the error output. Using either one in the cmd line below will work but not both.
Also tried with --from SELIANCIENS/Jones --to ERAVATE --credits 300000 --capacity 34 --ly-per 9.23

$ trade.py run --from SELIANCIENS/Jones --to "ERAVATE/Ackerman Market" --credits 300000 --capacity 34 --ly-per 9.23
Traceback (most recent call last):
File "./trade.py", line 102, in <module>
main(sys.argv)
File "./trade.py", line 76, in main
results = cmdenv.run(tdb)
File "c:\trade\commands\commandenv.py", line 80, in run
return self._cmd.run(results, self, tdb)
File "c:\trade\commands\run_cmd.py", line 840, in run
place.name() for place in restrictTo[0:-1]
TypeError: 'set' object is not subscriptable
 
Last edited:
Back
Top Bottom