Release Trade Dangerous (Est. 2015) Power user's highly configurable trade optimizer

Tromador

Tromador
Hi all.

Sorry for downtime earlier this week. The root partition on the host filled up and caused TD to behave in a weird way and because the actual real error (two lines of logfile) was buried in TD going insane (literally millions of lines of logfile) it took longer than it should to realise the real problem.

This has been corrected and shouldn't happen again. Certainly if it does, we'll know why next time.

We are planning a purge of the server data, pruning any data older than a month. We just don't see the point of keeping anything older, there's plenty of data in the past month to make pots of money trading, which is the ultimate point of TD, not an archive for stations not visited in years.

If you for any reason DO want this old data, you can still import it by using the spansh plugin (without the maxage parameter eyeonus mentioned above). Should you then visit such a station, the pale faces of strange evolving life forms staring with luminous eyes as you leave footprints in the dusty floor, that data (you do use EDMC or equivalent, right?) will get onto the server as it will be up to date.

This won't affect any data in your local databases, so if you want the leaner dataset, you'll need to delete your existing database and reimport, alternatively should you import spansh, what we send won't affect the old data you've accumlated.
This will happen next time the server does a spansh download, which will happen when spansh next releases a datadump. Certainly within 48 hours. When we do get to the purge, it might hang up the server as it has a lot to get through and delete. From then, it will automatically delete anything older than a month (well 30 days to be precise) to keep things reasonable.
 

Boulistar

B
Greetings CMDRs
First of all, congratulations for this very nice tool ! Big thanks to all people involved in the poject !

I have a question : is it possible to filter out carriers ?
I have updated everything first, so it may have added carriers though I should not have done that.
For the record here are the commands I have used :
python trade.py import -P eddblink -O all
"python trade.py run " "--capacity 736 " "--credits 3b " "--from shin/memo " "--ly-per 34 " "--empty-ly 45 " "--pad-size L " "--jumps-per 5 " "--hops 5 " "--max-days-old 1 " "--no-planet"
And here is what I got :
Shinrarta Dezhra/Jameson Memorial -> LTT 1873/Lippisch Hub Shinrarta Dezhra/Jameson Memorial: 736 x Basic Medicines, Nahuatl/Rigaux Vision: 736 x Tritium, No Cha/VFZ-2QT: 381 x Bromellite, 42 x Alexandrite, 17 x Grandidierite, 4 x Occupied Escape Pod, LTT 1873/Lippisch Hub: 736 x Tritium, No Cha/VFZ-2QT: 381 x Bromellite, 42 x Alexandrite, 17 x Grandidierite, 4 x Occupied Escape Pod, LTT 1873/Lippisch Hub +935 816 502cr (302 266/ton)
VFZ-2QT is of course a carrier.
 

Boulistar

B
It's working nice, thak you CMDR Ibizan !
I had already pretty much gone through the whole list of command line arguments (same page you have liked) but never found anything related to carriers. By the way searching for "fc" gives me nothing neither.
Is there an alternate doc, which is a bit more up to date ?
 

eyeonus

E
You can get the list of every option available for a command using -h, eg. trade run -h:
Code: 
Required Arguments:
  --capacity N          Maximum capacity of cargo hold.
  --credits CR          Starting credits.

Optional Switches:
  --from STATION, -f STATION
                        Starting system/station.
  --to PLACE, -t PLACE  Final system/station.
  --towards SYSTEM, -T SYSTEM
                        Choose a route that continually reduces the distance towards this system.
  --loop                Return to the starting station.
  --via PLACE[,PLACE,...]
                        Require specified systems/stations to be en-route.
  --avoid AVOID         Exclude an item, system or station from trading. Partial matches allowed, e.g. "dom.App" or "domap"
                        matches "Dom. Appliances".
  --direct              Assume destinations are reachable without worrying about jumps.
  --hops N              Number of hops (station-to-station) to run.
  --jumps-per N         Maximum number of jumps (system-to-system) per hop.
  --ly-per N.NN         Maximum light years per jump.
  --empty-ly N.NN       Maximum light years ship can jump when empty.
  --start-jumps STARTJUMPS, -s STARTJUMPS
                        Consider stations within this many jumps of the origin (requires --from).
  --end-jumps ENDJUMPS, -e ENDJUMPS
                        Consider stations within this many jumps of the destination (requires --to).
  --show-jumps, -J      Show detail of jumps between hops.
  --limit N             Maximum units of any one cargo item to buy (0: unlimited).
  --age DAYS, --max-days-old DAYS, -MD DAYS
                        Maximum age (in days) of trade data to use.
  --pad-size PADSIZES, -p PADSIZES
                        Limit to stations with one of the specified pad sizes, e.g. --pad SML? matches any pad, --pad M
                        matches only medium pads.
  --no-planet           Require stations to be in space.
  --planetary PLANETARY
                        Limit to stations with one of the specified planetary, e.g. --pla YN? matches any station, --pla Y
                        matches only planetary stations.
  --fleet-carrier FLEET, --fc FLEET
                        Limit to stations with one of the specified fleet-carrier, e.g. --fc YN? matches any station, --fc Y
                        matches only fleet-carrier stations.
  --odyssey ODYSSEY, --od ODYSSEY
                        Limit to stations with one of the specified odyssey, e.g. --od YN? matches any station, --od Y
                        matches only odyssey stations.
  --black-market, --bm  Require stations known to have a black market.
  --ls-penalty LSPENALTY, --lsp LSPENALTY
                        Penalty per 1kls stations are from their stars.
  --ls-max LS           Only consider stations upto this many ls from their star.
  --gain-per-ton MINGAINPERTON, --gpt MINGAINPERTON
                        Specify the minimum gain per ton of cargo
  --max-gain-per-ton MAXGAINPERTON, --mgpt MAXGAINPERTON
                        Specify the maximum gain per ton of cargo
  --unique              Only visit each station once.
  --loop-interval LOOPINT, -li LOOPINT
                        Require this many hops between visits to the same station. A value of 1 would be the default
                        behavior, so a value of 2 is the minimum allowed.
  --margin N.NN         Reduce gains made on each hop to provide a margin of error for market fluctuations (e.g: 0.25
                        reduces gains by 1/4). 0<: N<: 0.25.
  --insurance CR        Reserve at least this many credits to cover insurance.
  --routes N            Maximum number of routes to show. DEFAULT: 1
  --max-routes N        At the end of each hop, limit the number of routes that continue to the next round to the top N
                        highest scoring
  --checklist           Provide a checklist flow for the route.
  --x52-pro             Enable experimental X52 Pro MFD output.
  --prune-score PRUNESCORES
                        From the 3rd hop on, only consider routes which have at least this percentage of the current best
                        routes score.
  --prune-hops PRUNEHOPS
                        Changes which hop --prune-score takes effect from.
  --progress, -P        Show hop progress
  --supply SUPPLY       Only considers items which have at least this many units.
  --demand DEMAND       Only considers items which have at least this much demand.
  --summary             Summary layout of route instructions.
  --shorten             (Requires --to) Find the shortest route with the best gpt.

Common Switches:
  --help, -h            Show this help message and exit.
  --debug, -w           Enable/raise level of diagnostic output.
  --detail, -v          Increase level of detail in output.
  --color, -c           Add color to output for enhanced readability.
  --quiet, -q           Reduce level of detail in output.
  --db DBFILENAME       Specify location of the SQLite database.
  --cwd CWD, -C CWD     Change the working directory file accesses are made from.
  --link-ly MAXSYSTEMLINKLY, -L MAXSYSTEMLINKLY
                        Maximum lightyears between systems to be considered linked.
Note specifically:
--planetary PLANETARY
Limit to stations with one of the specified planetary, e.g. --pla YN? matches any station, --pla Y
matches only planetary stations.
--fleet-carrier FLEET, --fc FLEET
Limit to stations with one of the specified fleet-carrier, e.g. --fc YN? matches any station, --fc Y
matches only fleet-carrier stations.
--odyssey ODYSSEY, --od ODYSSEY
Limit to stations with one of the specified odyssey, e.g. --od YN? matches any station, --od Y
matches only odyssey stations.
Click to expand...
 
Last edited:

nepomuk

nepomuk
Hello @Tromador 🙋‍♂️, can you have a look ... There are problems with the download from your server.

1721548929874.png
 

Kraszus

Kraszus
I've installed TD and it seems to be working fine but when I update the database I got a lot of these warnings -
Code: 
INTERNAL ERROR: table Upgrade has no column named weight
CSV File: C:\Users\conor\data\Upgrade.csv:1061
SQL Query: INSERT OR REPLACE INTO Upgrade (upgrade_id,name,weight,cost) VALUES(?,?,?,?)
Params: ['1831', 'Hpt ATMultiCannon Fixed Large V2', '0', '0']
 

nepomuk

nepomuk
I also get an error when updating the listings. This is related to the carriers. If I start the update of the listings a second time, it goes through.
First run:
1723109880814.png

Second run:
1723110597823.png

:cool:
 

Kraszus

Kraszus
Getting this error every time I update the database, preceded with a lot of Warnings (WARNING: *** INTERNAL ERROR: table Upgrade has no column named weight):
Clipboard01.png
 

nepomuk

nepomuk
@Kraszus
I would recommend that you rebuild the database. You don't need old data anyway. It worked great for me, except for the double update of the listings.
But that's not a problem. I imported the Spansh database first, as Tromador's server was having problems at the time, and then updated the listings.
trade import -P spansh -O maxage=10 (Probably 5 days will be enough)
However, rebuilding the database should also work with eddblink.
https://github.com/eyeonus/Trade-Dangerous/wiki/Plugin-Options#options--o (options for eddblink)
 

amcb10

amcb10
Please help - I have installed Python but whet TD asks for the path and I point it to the exe I get an error, what am I doing wrong?

It is asking for Python Interpreter but I cannot find such file :(

Edit - Ran as admin and it now works but no commander profile and now wares to select in the drop down...
 
Last edited:

amcb10

amcb10
Yes I did that and it worked but there are no commodities listed in the dropdown and my profile cannot be located but it does not ask me where Elite is installed like it says it would.

Very frustrating....

I'll try again tomorrow.
 

nepomuk

nepomuk
... uh which dropdown list ? Do you perhaps mean the one from the TD-Helper ? It is no longer running. It would have to be adapted.
I have only worked with the CMD commands in the last few weeks. (e.g. trade buy --near amber --ly 40 --limit 20 --age 3 --fc N -P "Bauxite")
 

Tromador

Tromador
Shouldn't make any difference to you guys, but I have migrated the server to a new host running a newer version of CentOS. The old server was running a relatively ancient version and it was becoming a pain to support as all the system software was so old, I kept having to build new versions just for TD. Assuming all goes well, it's just DNS propagation and you guys shouldn't really notice any downtime or issues of any kind.

If you do encounter issues as a result of the migration, ideally please put a ticket on github as this forum is notorious for not emailing me when required and github always does.
 
You must log in or register to reply here.
Back
Top Bottom