Problems after data import for indicators
Viewing 6 posts - 1 through 6 (of 6 total)
-
Hello!
When building simple indicators from data that is not available in PRT I usually follow this procedure:
if date= 20161028 THEN volch= -754940902 elsif date= 20161031 THEN volch= -356964619 elsif date= 20161101 THEN volch= 20145996 elsif date= 20161102 THEN volch= -793765967 return volchThe market timeframe is set to standard with sundays showing.
Doing this I made the following observations and the question is: Is this a bug or something wrong with the code?
- All dates in the indicator are one day in the future, because PRT seems to move them one day back. You can see this in the file “Date_Bias.jpg” attached to this post. The value for the 28th October 2016 is displayed on the 27th October. As a consequence I moved all the dates in the indicator code by one day.
- Sometimes the indicator values are not displayed. In the attached screenshot the value for the 31st october (-356.964.619) is not displayed at all. It should appear on the 28th October.
- It is not possible to add standard indicators to the imported data with the sample code above. After changing the format like below at least simple moving averages can be applied but nothing more complicated. I do prefer the above version since it is saving code lines for import that are limited to 10.000. Is it possible to change this?
if date= 20050715 THEN volch= 543194284 endif if date= 20050718 THEN volch= 170619781 endif if date= 20050719 THEN volch= -395613980 endifThe indicator is attached for testing purposes. Please be aware that this thing takes some time to load.
- You are right, the date displayed is 1 day before what the “date” instruction is returning (attached screenshot example). I think it’s because “time” is returning 0 which is the first hour of the next day, keep in mind that all test made in data history is made only one time at Close of the candle, it may explain this difference.
- There is no 20161031 date returned by the “date” instruction, same situation as above.
- It could be possible to calculate moving average over past ‘volch’ data of course, just add these lines at the end of your code:
ma = average[20](volch) return volch, maDerek thanked this post
Viewing 6 posts - 1 through 6 (of 6 total)
- You must be logged in to reply to this topic.
New Reply
Summary
This topic contains 5 replies,
has 3 voices, and was last updated by 
9 years ago.
Topic Details
| Forum: | ProBuilder: Indicators & Custom Tools |
| Language: | English |
| Started: | 02/23/2017 |
| Status: | Active |
| Attachments: | No files |
Loading...