3/10/2023 0 Comments Copyq indicatorThe companies and services listed on this website are not to be considered a recommendation and it is the reader's responsibility to evaluate any product, service, or company. This NinjaTrader Ecosystem website is for educational and informational purposes only and should not be considered a solicitation to buy or sell a futures contract or make any other type of investment decision. Since these consultants are third-party services for NinjaTrader, all pricing and support information will need to be obtained through the consultant. You can locate the contact information for the consultants on their direct websites for any additional questions you may have. Once you have identified your consultants of choice, please visit each consultant's site for more information or contact them directly to learn more: Simply enter a consultant name or search by using our filter categories. You can search our extensive library of NinjaScript consultants through the link below. double test = High - Low would not be executed by the compiler and ignored as if it were a comment. In the case of my earlier replies in this thread, I used the terminology of "comment out" to mean place the // in front of lines that you don't want to execute, in effect making them the same as a comment. See Help Guide for additional information. Disable this property if your indicator requires custom values that cumulate with each new market data event. You would also see entire lines of comments that may be used to explain certain sections, for example: In C#, when you use // the compiler will not execute anything on that line after the //, so in C# the // is one way to comment what is going on in the code, for example:ĭouble test = High - Low // this is an example of a comment that would explain what "test" is If you are going to work in Ninjascript then you will want to become familiar with C# programming language as that is what Ninjascript is based on and the C# syntax governs everything. Thanks for your post and welcome to the NinjaTrader forums! (Note: if you have already changed the indicator, the line number above may not match so just refer then to the original Pivots indicator to verify/ find the specific lines of code needed to change in your indicator) To: public class PivotsType 1Converter : To: įrom: public class PivotsTypeConverter : The easiest way to deal with them is to comment them out from your indicator (lines 453 - 468).įor the type converter, it would be easiest to rename it. The enums have already been created by the original pivots indicator and they already exist in the indicators namespace. The error messages you posted are related to the the two public enums and the "TypeConverter". It sounds like you have created a copy using the process you did, there is a slightly easier way:ġ) open the indicator in the Ninjascript editorĢ) In the code of the Ninjascript file, right mouse click and select "save as"ģ) Enter new indicator/file name. This helps the community keep NT7 and NT8 items separate when searching. ~\Anaconda3\envs\vscodeds\lib\site-packages\pandas\core\generic.py in _get_label_or_level_values(self, key, axis)ġ561 values = _level_values(key).Please note we are asking all NinjaTrader8 posts to be placed in the NinjaTrader8 beta forums. > 1005 right_keys.append(right._get_label_or_level_values(rk))ġ007 # work-around for merge_asof(right_index=True) ~\Anaconda3\envs\vscodeds\lib\site-packages\pandas\core\reshape\merge.py in _get_merge_keys(self) ~\Anaconda3\envs\vscodeds\lib\site-packages\pandas\core\reshape\merge.py in _init_(self, left, right, how, on, left_on, right_on, axis, left_index, right_index, sort, suffixes, copy, indicator, validate)Ħ54 # validate the merge keys dtypes. ~\Anaconda3\envs\vscodeds\lib\site-packages\pandas\core\reshape\merge.py in merge(left, right, how, on, left_on, right_on, left_index, right_index, sort, suffixes, copy, indicator, validate) > 1 tourney_data = pd.merge(tourney_data, season_statistics_T1, on =, how = 'left') KeyError Traceback (most recent call last) But when I use season_statistics_T1.head().to_dict(). However, I got the key error message for season_statistics_T1, it worked just fine when get information using season_statistics_T1.head(). tourney_data = pd.merge(tourney_data, season_statistics_T1, on =, how = 'left') I tried to merge these two data frames as follows, which gives me the following error message. I have two data frames, tourney_data and season_statistics_T1.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |