+1 888 340 6572
MultiCharts Project Management
previous_open_issue.png
Go to the previous open issue
previous_issue.png
Go to the previous issue (open or closed)
star_faded.png
Please log in to bookmark issues
feature_request_small.png
Open Feature request MC-794

Allow optimization of boolean (true/false) inputs

action_vote_minus_faded.png
10
Votes
action_vote_plus_faded.png
next_issue.png
Go to the next issue (open or closed)
next_open_issue.png
Go to the next open issue
Description

Currently, there is no way to optimize an input that takes a boolean (true/false) as a parameter. When you attempt to optimize a signal that has a boolean input, that input is not shown in the "optimize inputs" dialog box. Rather, the signal will be optimized using whatever value you have currently applied for that signal.
  
E.g., assume that you have a signal with two inputs, with the following defaults:
  
   MovingAverageLength (100),
   AllowShortTrades(false);
  
If you attempt to optimize this signal, only the "MovingAverageLength" input will show up in the "optimize inputs" dialog box. It won't be obvious that there's a second input, "AllowShortTrades," and there isn't any way to run an optimization that uses values of both "false" and "true" for that input.
  
There's one workaround, namely using numbers as inputs in place of boolean values. I.e., to define the input with a default value of "0" instead of "false," and then use either "0" or "1" as an input to represent "false" and "true." Then you can optimize for both false and true by entering a range of "0 to 1" for that input in the "optimize inputs" dialog box. However, this isn't a great coding practice.
  
It would be better if MultiCharts could instead display boolean inputs in the "optimize inputs" dialog box, and give users a choice about whether to optimize those inputs. In that case, the user should be given options between something like "only true," "only false," or "both true and false" as the values for optimization. I.e., the user can force that input to be "true" for every simulation (without optimizing that particular input), "false" for every simulation (same), or optimized using values of "true" for some simulations runs and "false" for others.

Steps to reproduce this issue

See above.

Comments (0)
History
Issue basics
  • Type of issue
    Feature request
  • Category
    Usability
  • Targeted for
    Not determined
  • Status
    Under Review
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (3)
People involved
  • Posted by
    user-offline.png  Xyzzy (Xyzzy)
  • Owned by
    Not owned by anyone
  • Assigned to
    Not assigned to anyone
  • Subscribers
    1 subscriber(s)
    Click here to show the list of subscribers
Times and dates
  • Posted at
  • Last updated
Issue details
  • Resolution
    Not determined
  • Severity
    Normal
Attachments (0)
There is nothing attached to this issue
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates