Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Thu, 25 Apr 2024 12:48:44 +0000
[Locked] - Version 2151 Available: Foundation For Millisecond/Microsecond Timestamping
View Count: 12407
| [2020-08-16 11:02:57] |
| binaryduke - Posts: 359 |
|
I have a simple custom study that compares the current bar date/time to session times and also stores the last processed date/time value in PersistentSCDateTime variable. This compiles and works just fine on v2138. Compiling the same study on v2151 provides the following error during remote compilation: -- Starting remote build of Custom Studies Source files: DATETIMESTUDY.cpp. 64-bit -- 11:54:42 Allow time for the server to compile the files and build the DLL. The remote build did not succeed. Result: In file included from scstructures.h:98:0, from sierrachart.h:22, from DATETIMESTUDY.cpp:1: scdatetime.h: In function 'constexpr int64_t ADJUST(int64_t, int64_t)': scdatetime.h:147:1: error: body of constexpr function 'constexpr int64_t ADJUST(int64_t, int64_t)' not a return-statement } ^ scdatetime.h: In function 'constexpr double ADJUST(double, double)': scdatetime.h:156:1: error: body of constexpr function 'constexpr double ADJUST(double, double)' not a return-statement } ^ -- End of Build -- 11:54:44 Date Time Of Last Edit: 2020-08-16 11:03:42
|
| [2020-08-16 17:20:10] |
| User79074 - Posts: 105 |
|
I get the same error as post #25... I am not able to compile my studies in 2151.
Date Time Of Last Edit: 2020-08-16 17:23:15
|
| [2020-08-16 18:51:38] |
| gr93 - Posts: 18 |
|
Does this mean we can use sub-second time intervals in charts?
|
| [2020-08-16 18:55:28] |
| User907968 - Posts: 802 |
|
Similar error message using local build with debug from within Sierra Chart - g:\sierrachart_dev\acs_source\scdatetime.h(143): error C3249: illegal statement or sub-expression for 'constexpr' function g:\sierrachart_dev\acs_source\scdatetime.h(141): error C3259: 'constexpr' functions can only have one return statement g:\sierrachart_dev\acs_source\scdatetime.h(152): error C3249: illegal statement or sub-expression for 'constexpr' function g:\sierrachart_dev\acs_source\scdatetime.h(150): error C3259: 'constexpr' functions can only have one return statement No problem compiling in VS2019 or using MSVC v142 command line tool, and so far no problems in SC with recompiled code. |
| [2020-08-16 20:40:43] |
| |
|
Regarding post #25, we will have a new release out later this evening to resolve this. Does this mean we can use sub-second time intervals in charts? Yes but not right now. We will get to this as soon as possible.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2020-08-17 03:02:37] |
| |
|
We will be releasing version 2152 in about 10 minutes. This will resolve posts #25, #26 and #28. Although we think the problem in #28 is that the compiler you have installed, is too old. And does not support the language feature being used. We did make one change to the file naming format. We have added an _ in front of the the optional version number: [custom study file name]_2151.dll (32-bit) [custom study file name]_2151_64.dll (64-bit) We apologize for this, but this is our only opportunity to get the naming convention neat and clean. So we want to take advantage of this. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2020-08-17 03:03:21
|
| [2020-08-17 13:54:47] |
| User79074 - Posts: 105 |
|
Can you please confirm that with version 2152 there will be no more code breaking changes, so that we can calmly recompile our indicators and continue after that as usual?
|
| [2020-08-17 16:16:25] |
| binaryduke - Posts: 359 |
|
Trying to compile in v2153 yields this error relating to sc.VersionNumber: -- Starting remote build of Custom Studies Source files: buildtest_2151.cpp. 64-bit -- 17:15:12 Allow time for the server to compile the files and build the DLL. The remote build did not succeed. Result: buildtest_2151.cpp: In function 'void scsf_JAManagementLines(SCStudyInterfaceRef)': buildtest_2151.cpp:34:20: error: cannot convert 'const char [9]' to 'SCString (*)()' in assignment sc.VersionNumber = "20200816"; ^ -- End of Build -- 17:15:14 Date Time Of Last Edit: 2020-08-17 16:16:43
|
| [2020-08-17 16:29:33] |
| User79074 - Posts: 105 |
|
There is also another issue. I have compiled using 2153 successfully. I want to support both the old Sierra Chart and the new Sierra Chart. I need to include all the dll files for my customers. For example # Old Sierra Chart version test.dll test_64.dll # New Sierra Chart version test_2151.dll test_2151_64.dll Now If I include all the versions of the test dll indicator in a zip and they extract it into the new Sierra Chart data folder, you will see redundant indicators of test_64.dll and test_2151_64.dll, which looks cluttered and bad. Can you hide the test_64.dll indicator from the study view in the new Sierra Chart if there is a test_2151_64.dll there? That would solve the problem. Thanks. |
| [2020-08-17 19:20:54] |
| |
|
In regards to post #32, sc.VersionNumber is now function which returns SCString. In regards to post #33 we need to develop a solution to this. We will do that. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2020-08-17 19:21:03
|
| [2020-08-18 08:28:09] |
| binaryduke - Posts: 359 |
|
Re: post #34 & sc.VersionNumber, the same error is occurring in pre-release v2154.
|
| [2020-08-18 11:14:21] |
| |
|
This is not valid: sc.VersionNumber = "20200816"; This is not supported. Refer to:ACSIL Interface Members - Variables and Arrays: sc.VersionNumber Thinking about it, it is probably not unsafe but it serves no purpose. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2020-08-18 11:35:36] |
| binaryduke - Posts: 359 |
|
#36 My bad. Confused sc.VersionNumber with sc.StudyVersion. Apologies.
|
| [2020-08-18 11:42:57] |
| |
|
Now we have just updated the documentation for that member but still in the past that was not correct what the code was doing. But we would not expect it to cause any harm either.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2020-08-18 11:43:12
|
| [2020-08-18 12:49:57] |
| |
|
If you are using version 2154 and using the US equities data exchange with the Sierra Chart Exchange Data Feed you will now see true millisecond timestamps. This is still under development and is not fully implemented but it is now available. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2020-08-18 12:50:37
|
| [2020-08-18 13:45:21] |
| User79074 - Posts: 105 |
|
Has #33 been addressed? My customers are already asking me to compile the indicators on the new Sierra Chart, but I want to make sure I support both Old and New Sierra Chart so that there will be no confusion for customers.
|
| [2020-08-18 18:41:49] |
| |
|
Regarding post #40, yes this has been in the latest prerelease, 2154.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2020-08-19 16:30:49] |
| User220914 - Posts: 239 |
|
this is FANTASTIC thank you
|
| [2020-08-20 06:22:22] |
| |
|
We have done some additional ACSIL cleanup in version 2155, to be released. The following functions and data members have been removed: int AreTimeSpecificBars() int AreRangeBars() int AreNumberOfTradesBars() int AreVolumeBars() int AreRenkoBars() int AreReversalBars() int ArePriceChangesBars() int AreDeltaVolumeBars() int ArePointAndFigureBars() sc.NumberOfTradesPerBar sc.VolumePerBar sc.RenkoTicksPerBar sc.ReversalTicksPerBar sc.PointAndFigureBoxSizeInTicks sc.PointAndFigureReversalSizeNumBoxes sc.RenkoTrendOpenOffsetInTicks sc.RenkoReversalOpenOffsetInTicks sc.DeltaVolumePerBar sc.PriceChangesPerBar sc.DailyDataBarPeriod sc.DaysPerBar sc.RangeBarValue sc.RangeBarType sc.MonthsPerBar These functions and members have been out of date now for years and have been documented as being deprecated during all of that time. The replacement function to access this data is: sc.GetBarPeriodParameters() The following text string members are now changed to functions: SCString sc.VersionNumber(); SCString sc.UserName(); SCString sc.DataFilesFolder(); SCString sc.ServiceCodeForSelectedDataTradingService(); SCString sc.SCDataFeedSymbol(); SCString sc.CustomAffiliateCode(); SCString sc.ChartbookName(); SCString sc.ChartTextFont(); This is now a function: n_ACSIL::DTCSecurityTypeEnum sc.SecurityType(); There are two reasons for this code cleanup. One reason is just to remove members which are just out of date and deprecated and the other reason is to improve performance and improve code safety. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2020-08-20 20:58:53
|
| [2020-08-20 08:06:23] |
| User79074 - Posts: 105 |
|
Is that the end of code breaking changes requiring indicator recompilation or will there be more?
|
| [2020-08-20 10:22:29] |
| |
|
Yes this is all and we are releasing version 2155 in about 20 minutes.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2020-08-20 12:30:36] |
| |
|
We expect to have a full release of the microsecond time stamping functionality, released over this weekend at least on half of the servers. Trades will be timestamped to the millisecond and microseconds will increment by 1, for each trade within the same millisecond. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2020-08-20 12:31:18
|
| [2020-08-20 13:26:51] |
| User79074 - Posts: 105 |
|
I replaced sc.UserName with UserName() and there is a compilation error error: 'UserName' was not declared in this scope Same thing with ChartbookName(), doesn't work either. |
| [2020-08-20 15:25:23] |
| Ackin - Posts: 1865 |
|
We expect to have a full release of the microsecond time stamping functionality, released over this weekend at least on half of the servers.
What version of Sierrachart will be needed for that? 2151? |
| [2020-08-20 17:03:04] |
| |
|
I replaced sc.UserName with UserName() and there is a compilation error Use: sc.UserName()
As you can see the change is very simple. What version of Sierrachart will be needed for that? Any version. But 2151 or higher is needed to receive the microsecond timestamps. Really the user should be on 2156.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2020-08-20 20:57:43
|
| [2020-08-20 21:57:42] |
| ejtrader - Posts: 688 |
|
SC Team - What are the new functions for the following (version 2154 was the last version supported these functions)? sc.AreTimeSpecificBars() sc.RenkoTicksPerBar Thanks |
To post a message in this thread, you need to log in with your Sierra Chart account: