Jump to content

Welcome to the new Traders Laboratory! Please bear with us as we finish the migration over the next few days. If you find any issues, want to leave feedback, get in touch with us, or offer suggestions please post to the Support forum here.

flyingdutchmen

Members
  • Content Count

    114
  • Joined

  • Last visited

Personal Information

  • First Name
    TradersLaboratory.com
  • Last Name
    User
  • City
    amsterdam
  • Country
    Netherlands
  • Gender
    Male

Trading Information

  • Vendor
    No
  1. Making consistent returns daytrading the ES is a lot harder than most think... in fact it might be the hardest game in town but for some reason it's what the mayority of internet forum readers want to do. maybe it's partially about being a badass ("I'm an S&P trader") but it's much harder than trading has to be. The S&P futures are usually one of the most random and noisy markets out there.
  2. using a simple litle function in tradestation you are able to convert ticks to any timeframe you wish, eliminating the fact that you must use 2 or more charts with different tf's in order to gather data from multiple tf's. all can be done within the tickchart
  3. what you could do, is to write your skript on 1 ticks, you will need a function to convert the single ticks to one minute bars so you can keep using timeframe based indikators. this is fairly easy and this way you will not have to wait a full minute before you can re-enter the next trade. this option is available but i recommend it only if you do not need long history for backtesting and stuff. once you know you have a valid strategy which works for you, and you do need timeframe based calculations this is the way i would go. it will decrease your waiting from a minute to a tick, will that do?
  4. there are plenty people here who are familiar with el, meself included. it would be helpfull if you would give some details about what you are trying to archieve.
  5. well, by being able to export the data in a format which can be imported by TS without further modifications, i am able to plot constant range bars from tick-data, at least for the visual part. from here i would be able to use further calculations onto those range bars like finding swing high's/low's which wasnt possible in TS, at least not standard. timebased swing highs and low do not have the same quality. this is just a workaround. It filters out alot of noise and give me more quality swings. i did not like the MC rangebars so i made my own in TS which do fit my conditions
  6. Constant RangeBars for TradeStation
  7. Outcome: Constant RangeBars for TradeStation, Been done before ?
  8. I am aware there allready is an active tread about rounding numbers but it is not working for me, i am facing somewhat the same problem when printing a to a TXT-file, this solution rounding to price does not work for me as am im trying to round time or any number not correlated to price in a text file i am trying to make tradestation to manipulate the price of a certain underlying and print the full numbers incl Hour and Minute in a text file so they can later be imported as 3d party ascii data without needing to do some workaround with open office example... Variables: myvalue(0); myvalue = mavalue + 1; Print(File("c:\TradeStationDataExport\TS_Data.txt"), myvalue); the text file will allways be filled with 2 decimals behind the number myvalue Output in TXT File: 1.00 2.00 3.00 Needet: 1 2 3 i have tried pretty much all rounding functions (and ofcourse the simple Round reserved word) i could get my hands on and i made up some myself, unfortunally this seems not to work while printing data to an TXT-file. Thoughts ?
  9. a possible solution to being able to tell what price it will need in order to change direction is to stick it in a loop and let it find out itself. i am not sure what you are trying to achieve, if for example your indikator, which in this case is the hull ma is pointing up and you would want to know how much price should move down in order to make your indikator go down or cross below some fix point whithout knowing or needing to know the exact calculations it shouldnt be to hard to find out. stick the calculation in a loop and let it loop trough untill your disired outcome is calculated, this will then be the price you will need to achieve the theoretical change in the indikator you would like to see. but then again, imho it is not very helpfull to use an indikator from which one does not know on which formula's it is based. if you need help let me know this should not be very hard to realize, im not sure if it is what you are trying to achieve here
  10. the idea of this litle script is that on each bar it will take the current value and the value of n bars back and by the difference over those n bars it will create a "virtual" and "straight" line from your MA n bars back to the MA of currentbar and then messure the difference from the MA to that virtual line. if the difference is greather that the virtual line incl the tollerance on of those bars the counter will never be equal to n, therefore condition will stay set to false.all bars must stay within this tollerance in order to set the counter equal to n
  11. i still owe you an anser on this one, sorry it took me a while to reply. you where asking for an easy and fast way to check if your slope is within tollerance, here is a small script which you could save as a false/true function if it is what you are searching for. read the examples i have wrote in the brackets.this skript may be a bit hard to understand at first but it is pretty logical and simple. it uses a 50-period sma to be your line and calculates the difference between the value of the current bar and n bars back dividet by n, this gives the value each bar should go up or down to meet your creteria and will be used to check all other bars within a loop inputs: n(5), toll(.5);{tollerance in percent of difference} variables: result(0), diff(0), index(0), counter(0); result = average(close,50);{something we will use as a line} diff = absvalue(result-result[n]) / n;{absolute difference between current value and value n bars back devidet by n} counter = 0;{set counter to zero} if result > result[n] then begin{first loopblock in case of current value being higher same value n bars back, second block visa versa} for index = n-1 downto 0 begin if result[index] >= result[n] + ((n-index)*diff) - (toll*diff) and{make sure each bar coming in after n is higher but not higher then the tollerance} result[index] <= result[n] + ((n-index)*diff) + (toll*diff){make sure each bar coming in after n is lower but not lower then the tollerance} then counter = counter + 1;{counting in case of succes} end; end else for index = n-1 downto 0 begin if result[index] <= result[n] - ((n-index)*diff) + (toll*diff) and result[index] >= result[n] - ((n-index)*diff) - (toll*diff) then counter = counter + 1; end; condition1 = counter = n;{if succesfull counter should be equal to n after having all bars calculated} if condition1 then plot1( result );{show if succesfull} in case of a sideways market the statement (toll*diff) could be a bit to narrow because the difference between current value and the value of n bars back is nihil, and therefore give less signals. this you could change by (toll*value[index+1] to give more signals in case of a "straight" slope in a sideways market. it will take a percentage of the value 1 bar ago within the calcuation of the loop, adapt the input to it.
  12. sorry i didnt get to it yet. have fun with MC, must be a great software from what i hear about it
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.