<- Back to Tasks

"Global Variables" task for Custom Projects

So if you've ever worked with SQL Server's DTS packages feature, there's a task for establishing Global Variables. It would be awesome  if we had something like this for Custom Projects.



Presently I have to clone/configure a Custom Project every time I change just about anything - the instrument, timeframe, build params, etc, etc. This ends up producing an ungodly number of Custom Projects. Worse, if I ever want to make a fundamental change to my workflow that would apply to multiple projects, I have to update them individually. Big time sink.


The solution would be to have a task to set/update global variables, and to let the various tasks (Build, Retest, and Optimize being the most critical) take advantage of those user variables.


The "Go To Task" task should also be able to look at these variables. This would create the ability to use conditional logic, which in my opinion greatly increases the "programmability" of the Custom Projects.


Finally, it would be super sweet if you could configure multiple combinations of settings for your global variables, and if you could choose the combination you want to use upon running the project.


For example:


Combo 1:
Instrument Var: EURUSD
Timeframe Var: H1


Combo 2:
Instrument Var: USDJPY
Timeframe Var: H4


I realize that it's complex because every Task has a unique set of fields that could possibly be parameterized. If only the fields on the Data tab were parameterized I think we'd have a solution that get's us 90% of the way.


Thanks for your consideration!



Ryan





Attachments
No attachments
  • Votes +2
  • Project StrategyQuant X
  • Type Feature
  • Status Archived
  • Priority Normal
  • Assignee None

History

RH
#1

rhartstein

15.06.2019 03:13

Task created

t
#2

tnickel

15.06.2019 11:29
Voted for this task.
t
#3

tnickel

15.06.2019 11:30

I think it makes sense, but I think it is not so easy to implement.

a) global variable for currency and timeframe?


b) global variable for start-end date


but this is very helpfull

RH
#4

rhartstein

15.06.2019 18:59
Yes, the fields on the "Data" tab - instrument, timeframe, spread, slippage, etc. would I my opinion be most important to parameterize, as it would allow us to apply the same Custom Projects to multiple instrument scenarios.


But to take it a step further - if parameterizing all the various fields of all tasks is difficult (and I assume it would be, simply from a UI standpoint), how about this idea...


Could we have a "Scripting" task that allows us to access the various Tasks programmatically and update their values there? The task would need to be able to use variables set in the Global Variables task and apply them to objects of the user's choosing. 

PV
#5

Cornus

17.06.2019 08:57
Voted for this task.
MF
#6

Mark Fric

20.10.2020 14:38

Status changed from New to Archived

we have different priorities now.


We wil be adding possibility to simply modify symbols an timeframes in the whole custom project in build 130, wich would partly solve the need for a lot of editation after cloning.

Votes: +2

Drop files to upload

or

choose files

Max size: 5MB

Not allowed: exe, msi, application, reg, php, js, htaccess, htpasswd, gitignore

...
Wait please