Opcje linii komend
Przykłady:
TashaCL.exe "Data\Scenarios\PDDemo\Problem1.ini"
TashaCl.exe -s SQLServer -c "SERVER = (local)\SQLEXPRESS; DATABASE = Tasha; user id = sa;password = password;" -an -nScenario* -i25000 m20 -thigh -l1 -g0 -r"C:\RunReport.txt" -j"C:\IterationsDetails.txt"
TashaCL.exe -s SQLite -c "C:\PerformanceTesting.s3db" -ay -nScenario* -i25000 -tmedium -z40 -q10 -x200 --RestartPhasesCount=5 --RestartPhasesPercentage=20 -l1 -r"C:\RunReport.txt"
| Prefix | FullCommand | DefaultValue | Required | Description |
| a | multithreading | y | No | Allow use of multiple processors. y / n |
| b | logbestsolution | n | No | Log every best found solution. y / n |
| c | connectionstring | Yes | Database connection string or folder name. | |
| d | distances | "" | No | The full name of the file that distances are created from. Use if you use only one such file. Equals setting the DistanceFileName1 option. |
| g | neighbourhood | 0 | No | One of the solver options. Specify the neighbourhood size. |
| h | heuristicspath | "" | No | One of the solver options. Specifies directory where heuristics creation information is stored. |
| i | iterations | 25000 | No | One of the solver options. How many iterations should be run |
| j | iterationreport | "" | No | One of the solver options. Expects file name and will produce a detailed solver run report in it. |
| l | logginglevel | 0 | No | How much progress information you want to see. 0 .. little |
| m | secondstorun | 0 | No | One of the solver options. How many seconds will the the solver run for before stopping. |
| n | inputscenarioname | "" | Yes | Scenario name or file name. This can also be a mask such as * which will run all scenarios in the datasource. You can use ; to enter multiple masks. If import mode is selected, this will be the name of the newly created scenario. |
| o | solver | "" | No | Solver options. If not specified SolverOptions.xml will be used. If that is not present it will get created. |
| q | iterationswithnoise | 0 | No | One of the solver options. Specifies percentage of solver options that should be run with noise turned on to enhance variability. |
| r | runreportfilename | "" | No | Prints out solving report if specified. |
| s | source | SQLite | Yes | SourceType of scenario/s. Current allowed types are 'MsSql', 'SqlLite', 'PostgreSql'. Pre PostgreSql (cca 2020.1.813) Tasha CL supports only 'SQLServer' / 'SQLite'. |
| t | temperature | MediumHigh | No | One of the solver options. How high should the starting temperature be. Select one from UltraHigh, CrazyHigh,High, MediumHigh, Medium, MediumLow, Low |
| UsePairHeuristics | n | No | Hodnota y přidá řešiteli použití párových heuristik. Vhodné pouze v určitých situacích, kde se vyplatí vkládat Zakázky v blízkých párech protože samostatně by nebyly tak výhodné (například kvůli vysoké fixní ceně vozidla). Vhodné vyzkoušet v situacích volné heterogenní flotily. | |
| v | UseVehicleSwapsHeuristic | y | No | Use the vehicle swap heurisitic or not. Not using it can make the solver run faster, when large number of vehicles are involved. |
| w | wait | 0 | No | How long should the program wait after solving is finished. -1 = until key is pressed. |
| x | stayatbestforx | 0 | No | If set to higher than 0, the solver will always allow only better solutions after a new best solution is found. Default = 0. |
| y | returntobestafterxnonimproving | 0 | No | If set to higher than 0, the solver will return to the best solution if it cannot find an improvement for that many iterations. Default = 0. |
| z | onlydistancecostiterationspercentage | 0 | No | If set to a number between 1 and 100 the solver will have phase where it ignores distance costs |
| MaxProcessorCount | 0 | No | If set to a greater than zero, the solver will not use more than the number of processors. | |
| RestartPhasesCount | 0 | No | If set to a number between 1 and 100 the solver will have phase where it ignores distance costs. | |
| RestartPhasesPercentage | 0 | No | If set to a number between 1 and 100 the solver will have phase where it ignores distance costs. | |
| ExportSolutionPath | false | No | If set to true will try to export solution (using the standard exporter) based on the scenario and solution name. | |
| DistanceFile1 | No | |||
| DistanceFile2 | No | |||
| DistanceFile2 | No | |||
| HereMapsAppId | Needs to be set with the right value for App Id (provided by a HERE Maps reseller) in order for Here maps update distances and mapping displaying to work. | |||
| HereMapsAppCode | Needs to be set with the right value for App Code (provided by a HERE Maps reseller) in order for Here maps update distances and mapping displaying to work. | |||
| HereMapsTileLayerType | Base | One of the layer types that can be displayed: Base, Grey, Hybrid, Traffic, Truck, ReducedDay, BaseNoLabels, Satellite, Terrain | ||
| Mode | solve | No | Can be one of the solve, edit, import, export, update, geocoding, distances, report, command. | |
| PluginName | No | |||
| PluginSettings | No | |||
| ImportFile | No | |||
| PlanningDate | No | |||
| ScenarioName | No | |||
| ExportFile | ||||
| ReportFile | ||||
| PrefixSolution | No | Text to prefix created solutions with. | ||
| SolutionName | No | The solution name that will be used. (import - reconstruction, report creation, exported solution). Mask can be used (eg. 1*). If no solution name is provided the latest solution is used. If Best is given as a parameter, best solution is chosen. If BestFeasible is given as a parameter, best feasible solution is selected. | ||
| CommandName | No | The name of the command from the plugin defined in PluginName. If incorrect TashaCL will list all available commands. | ||
| TrackingCompany | No | Company for Tracking plugin. | ||
| TrackingLogin | No | Login for Tracking plugin. | ||
| TrackingPassword | No | Company for Tracking plugin. |
Przykłady użycia
Obliczenia podstawowe
TashaCl.exe -s SQLServer -c "SERVER = localhost\sqlexpress; DATABASE = tasha_461;Integrated Security=SSPI;" --logginglevel 1 --Mode geocoding --PluginName SolverTech.Tasha.Plugins.Geocoding.HERE --HereMapsAppId "kAOeFVm2aPiGSP2bea7Z" --HereMapsAppCode "TDUd3elgqc0VQNEceejeLD" --inputscenarioname *
Tasha odczytuje wszystkie scenariusze w bazie danych tasha_461 i ogeokoduje adresy za pomocą HERE.
TashaCl.exe -s SQLServer -c "SERVER = localhost\sqlexpress; DATABASE = tasha_461;Integrated Security=SSPI;" --logginglevel 1 --Mode distances --PluginName SolverTech.Tasha.Plugins.UpdateDistances.HERE --HereMapsAppId "kAOeFVm2aPiGSP2bea7Z" --HereMapsAppCode "TDUd3elgqc0VQNEceejeLD" --inputscenarioname *
Tasha czyta wszystkie scenariusze w bazie danych tasha_461 i oblicza macierz odległości używając HERE.
TashaCl.exe -s SQLServer -c "SERVER = localhost\sqlexpress; DATABASE = tasha_461;Integrated Security=SSPI;" --logginglevel 1 --Mode solve --inputscenarioname * -i10000 -tMediumHigh -z0 -ay --MaxProcessorCount 0 --RestartPhasesCount 5 --RestartPhasesPercentage 30
Tasha odczytuje wszystkie scenariusze w bazie danych tasha_461 i oblicza rozwiązanie przy 10000 iteracjach, temperaturze MediumHigh, 5 fazach restartu, 30% fazach restartu i przy użyciu wszystkich dostępnych procesorów.
Jeśli powyższe polecenia zostaną umieszczone w jednym pliku .bat i uruchomione w podanej kolejności, Tasha stworzy rozwiązanie z zaimportowanych scenariuszy.
Generowanie raportów:
TashaCl.exe -s SQLServer -c "SERVER = localhost\sqlexpress; DATABASE = tasha_461;Integrated Security=SSPI;" --logginglevel 1 --Mode report --inputscenarioname "rozvoz - 15.10.2019" --SolutionName * --ReportLayoutFile "Report.repx" --ReportFile "rozvoz - 15.10.2019.pdf" --HereMapsAppId "kAOeFVm2aPiGSP2bea7Z" --HereMapsAppCode "TDUd3elgqc0VQNEceejeLD" --HereMapsTileLayerType "Base"
Tasha łączy się z bazą danych tasha_461, pobiera scenariusz dostawy - 15.10.2019 i tworzy raport pdf zgodnie z szablonem raportu w Report.repx.
Zauważ, że chociaż parametry --inputscenarioname i --solutionname obsługują symbol wieloznaczny * (i załadują wszystkie scenariusze/rozwiązania), parametr --reportfile nie. Ze składnią --reportfile *.pdf Tasha nie utworzy żadnego raportu, ze składnią --inputscenarioname * --SolutionName * --ReportLayoutFile "Report.repx" --ReportFile report.pdf Tasha utworzy raport.pdf używając ostatniego scenariusza i rozwiązania (odpowiednio dla pierwszego rozwiązania pierwszego scenariusza utworzy plik report.pdf, który zostanie nadpisany przez drugie rozwiązanie pierwszego scenariusza...).
Podczas generowania raportu należy mieć tylko jeden plik *Face.dll w folderze "Plugins".