| sfjeff |
|
Gold User, Member, Platinum User, TeleChart
|
| Registered User |
|
|
|
|
| Unsure |
|
| Wednesday, September 28, 2005 |
| Saturday, June 19, 2010 11:14:47 AM |
54
[0.02% of all post / 0.01 posts per day] |
|
William - Is there a reason you need to scan for multiple conditions? Why not create a combo condition that can be backtested and provides a natural organization structure for the rules you want? Why have two different places where you keep rule logic: 1) in the rules themselves and 2) in the watchlist where you have multiple conditions contributing to flag and sort order independently. If you keep all logic associated with the condition you are interested in inside a main "My signal condition", it becomes a discrete object that can be dropped on watchlists or backtesters while maintaining semantic integrity. IMO, scanning for multiple conditions confuses the user interface without providing any functionality that is missing from combo conditions (except for the true x of y recent bars in combos, which would be a nice addition, but is not something I rely on to be honest).
|
|
If there was even a way to generate approximate values inside SF, that would be useful.
|
I have a system that works better if I incorporate industry data. To do this, I add Industry price history as an indicator to my chart and then add sub-indicators for the elements of my system. My system works well if I make trading decisions near the end of the day based on the price bars up to that point. Industry intraday price data is empty for the current day, so my system signal does not match the actual system I have backtested.
Is there a way to create a signal based on Daily industry price data that incorporates the current day shortly before close?
|
|
Please note that this was not just a Worden Brothers issue, but an issue at the major stock exchages NYSE went to entirely human trading for a period.
Many of the most profitable trades have been cancelled and anyone who took profits early was likely left with a possibly unfortunate short position, so the loss of timely information here was a lot smaller than it would seem at first glance.
I'll grant you that this would be very frustrating, though.
|
|
Thank you! This makes the product much more usable and will save me some time during that critical half hour from 12:30-1:00 PST.
|
Could you also try uninstalling the data and re-installing it? That has fixed some very strange problems for me (At least for a while).
Also, does your system page a lot? You can see this by running "Task Manager" (type it in the windows start menu find box and select Windows task manager), going to the Processes tab, and adding page faults using View->select Columns. Page Faults is a cumulative number and PF Delta is what is happening right now. What it means is (oversimplifying a bit), you ran out of memory and stored some of your program's memory on disk and Windows has to stop and get that memory back before the program can continue to run. If you are routinely seeing more than 1000 under PF Delta, then that means your computer could probably get a significant performance boost from either upgrading your ram or closing programs that are using a lot of memory (in practice this can mean closing web browsers that are competing with Stockfinder for memory if you have a lot of windows open.)
The reason I bring this seemingly unrelated issue is that frequently subtle bugs that go unnoticed when things are going normally can suddenly have large impact when you add these memory-fetching pauses. I think that when I had the issues that were fixed by deleting and re-creating my stockfinder data, the issues started when I was short on memory for a good period.
|
|
By the way, it looks like an effective workaround for the issue with colors not painting is to open up the condition all the way.
|
|
More issues with this.
Using {} to separate separate conditions and () to group within an atomic condition, I saved the following condition structure:
(ph and {{IndA and IndB and IndC} or Ind2}) or (stoch1 and stoch2 and stoch3 and {{IndA and IndB and IndC} or Ind2})
Looking at the layout I sent, this is "SM 21 Option Sell".
When it reconstituted on a new graph, the two nested conditions got flattened into something strange that you probably have to read the blocks diagram to understand (I see the nouns, but not the verbs). You can duplicate this with the layout I emailed, but at least one issue is that the IndB condition seems to refer to the main graph now instead of the industry graph.
Apologies for the editorial comment, but this would make a great unit test.
|
Alright. Email sent.
Jeff
|
|
oops. Posted in chrome again...sorry about that.
|
|