Mathew

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 90 total)
  • Author
    Posts
  • in reply to: Eclipse Tool #55003
    Mathew
    Mathew
    • Topics: 16
    • Replies: 1,057
    • Posts: 1,073

    Hi Thomas,

    Thanks for that – I can see the issue but can not promise a speedy response as 1.5 is locked for release.

    What I would suggest is that you add a ShowBar tool and set the script to ECL(ECLIPSE=Solar)

    Then you can change the display from Arrows to Lines and set the width and transparency.

    Once you have it all the way you like it, save it to the tool bar (see https://help.optuma.com/kb/faq.php?id=576) so you can get it easily.

    NOTE: This is not showing events in the future but that is something that I see as a bug and will get that actioned straight away.

    All the best

    Mathew

    solar

     

    in reply to: Three Cheers for Optuma Scripting #54989
    Mathew
    Mathew
    • Topics: 16
    • Replies: 1,057
    • Posts: 1,073

    Thanks Andy -we all really appreciate you writing this.

    We’ve also been a little surprised with all that Scripting can do. Initially it was written as a way to access functions programmed in the Pascal module. My expectation was that Pascal would be what everyone uses. As time went on, we realised that scripting could do 99% of what people needed so we made that the priority.

    All the best

    Mathew

    in reply to: Eclipse Tool #54967
    Mathew
    Mathew
    • Topics: 16
    • Replies: 1,057
    • Posts: 1,073

    Hi Thomas,

    Those options are not needed on this tool. It is only symbols, so it makes no sense to show/hide them when that can be done by adding/deleting the tool.

    This tool also has separate Solar Colour and Lunar Colour to distinguish between the two types of Eclipses.

    If there is a use case on this which I am not considering please let me know.

    All the best

    Mathew

    in reply to: Script Processing Efficiency #54959
    Mathew
    Mathew
    • Topics: 16
    • Replies: 1,057
    • Posts: 1,073

    Hi Andy,

    Quick answer is no – it does not stop. The reason is that we use what we call vector scripting. That means for each calculation we don’t just have a single value but a complete history of that calculation through time. That’s why you can add a script like this in a Show Plot and see when it was true in the past. To even get a value for today, we need the full history in case today’s value was dependent on the history (like in a weighted moving average).

    The optimization you are talking about makes sense when there is only a single value, but not in this style. The extra milliseconds which would be saved is not worth the weeks of development it would take us to implement that. Instead our focus is on keeping the processing of the vectors as fast as possible.

    All the best

    Mathew

    in reply to: "Years" period in the Time Measure tool #54907
    Mathew
    Mathew
    • Topics: 16
    • Replies: 1,057
    • Posts: 1,073

    Hi Thomas,

    I can’t see any issues with this but I doubt it will make version 1.5 as that is starting to be rolled out.  There is no ETA on 1.6 at this stage but I imagine it would be early next year.

    All the best

    Mathew

    in reply to: Searching through natal aspects #54875
    Mathew
    Mathew
    • Topics: 16
    • Replies: 1,057
    • Posts: 1,073

    Hi Joseph,

    The solution is not as simple as referencing the first date in the file because we don’t have full history for all codes. I’ve always been hesitant to program that in if it was not 100% correct.

    What I am planning is an internal database of first trade dates for companies and having it so that the NA() script and tool can reference that. Ideally I would also like a way that users have control over the dates in case they want to make their own adjustments.

    It is part of what I am planning for an Astro overhaul which will happen in the new year.

    All the best

    Mathew

    1 user thanked author for this post.
    in reply to: Property Panel Variables #54795
    Mathew
    Mathew
    • Topics: 16
    • Replies: 1,057
    • Posts: 1,073

    Hi Trevor,

    The issue with this is that the variable “#$FudgeFactor” is a single number where all the other data sets we work with are arrays of numbers.

    Regardless we are looking at adding a function that will take a single number and create a data list from it. If it all goes smoothly we should be able to add it into Optuma 1.5 which is due in Q4.

    All the best

    Mathew

    in reply to: Script Manager – Strange Behaviour #54767
    Mathew
    Mathew
    • Topics: 16
    • Replies: 1,057
    • Posts: 1,073

    Hi Trevor

    The issue is that Show Bar used to only show Boolean results. So we hid any scripts which were not a Boolean. If your script was

    Signal = SWINGSTART(GS) > SWINGSTART(GS)[1];

    Then you would see it.

    With the ability to show numbers in ShowBars, we do need to do a check to see if this is working ok.

    Hopefully that explains what is happening.

    All the best

    Mathew

    in reply to: Chart Price Unit linked to a variable #54741
    Mathew
    Mathew
    • Topics: 16
    • Replies: 1,057
    • Posts: 1,073

    Hi Joe,

    I don’t think so. We do have variables (see https://help.optuma.com/kb/faq.php?id=964) but they can not be a formula. To add that would take a lot of work but let me run it past the other developers. If anything changes we’ll post an update.

    All the best

    Mathew

    1 user thanked author for this post.
    Mathew
    Mathew
    • Topics: 16
    • Replies: 1,057
    • Posts: 1,073

    Hi Andrew,

    Put your script into a variable – it does not matter what you call it. Remember the semi-colon at the end

    Then use the NoRepeat function on that variable set to 7 bars (or 5 if you want trading days). See here for more help https://help.optuma.com/kb/faq.php?id=1031

    v1 = CLOSE(OFFSET=2)<CLOSE(OFFSET=1) AND CLOSE(OFFSET=1)<CLOSE();

    NoRepeat(v1, BARS=7)

     

    Another tip. You could change your line to be this

    v1 = CLOSE()[1] IsUp AND CLOSE() IsUp;

    That is telling Optuma the previous bar needs to be a higher close and the current bar needs to have a higher close.

    Hope that helps

    Mathew

     

     

    1 user thanked author for this post.
    in reply to: Last report date of financials (Fundamental field) #54135
    Mathew
    Mathew
    • Topics: 16
    • Replies: 1,057
    • Posts: 1,073

    Hi Karen,

    We double checked our Fundamental supplier and that date is not listed in what they give us. I have no solution on this in the short term.

    All the best

    Mathew

    in reply to: Using a dynamic POWER function calculation #54133
    Mathew
    Mathew
    • Topics: 16
    • Replies: 1,057
    • Posts: 1,073

    Hi Dean,

    The way we set up variables was to treat them as single numbers (not an array of numbers). Because of that the prior values are ignored and it will only show as the last value.

    Something to keep in mind with Optuma is that we do not run each line in the script for each bar but we fully calculate each line. So this line

    $months = FLOOR((BARDATE() – startDate) / daysPerMonth) + 1;

    is fully calculated before the final line is calculated.

    The use of the variables was so we can have $a = 50 and that would allow me to have bars=$a through my code.

    Side note: if you make it #$a = 50; then the “a” will show up in the properties panel.

    So what is the solution?

    Have a running total of the number of months:
    M1 = FLOOR((BARDATE() – startDate) / daysPerMonth) + 1;
    This is an array instead of a single value.

    Use an IF to compound when the month changes
    CMGRTotal = If(M1 <> M1[1], CMGRTotal[1] * CMGR, CMGRTotal[1]);

    What that is saying is if M1 is different from the previous value (M1<>M1[1])
    then multiply our previous value by the CMGR (CMGRTotal[1] * CMGR)
    else Set the value to the same value as last time (CMGRTotal[1]).

    Then you can multiply that by the start value.

    All of this is untested but it should set you in the right direction.

    All the best

    Mathew

    in reply to: Natal Chart Functionality #54113
    Mathew
    Mathew
    • Topics: 16
    • Replies: 1,057
    • Posts: 1,073

    Hi Trevor,

    I am hoping to spend some time focusing on these later in the year, I can mark it as something to investigate then.

    All the best

    Mathew

    in reply to: Last report date of financials (Fundamental field) #54071
    Mathew
    Mathew
    • Topics: 16
    • Replies: 1,057
    • Posts: 1,073

    Hi Karen,

    After doing a quick check through the data we are getting I don’t see the last reporting date listed. Unless it goes by a different name I do not think that we have it.

    All the best

    Mathew

    in reply to: Automatically calculate public holidays from 1900-2203 #54069
    Mathew
    Mathew
    • Topics: 16
    • Replies: 1,057
    • Posts: 1,073

    That’s Awesome Dean, thanks so much for sharing.

Viewing 15 posts - 1 through 15 (of 90 total)

Pin It on Pinterest

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.

Close