StockFetcher Forums · View by Author: (267 messages)  [ Display By: Date / Subject ]<< 1 2 3 4 5 ... 27 >> 
Filter Exchange · Can we get filter results emailed in .csv format?
tomb
msg #106516
6/4/2012 2:57:16 PM

This should not be a problem at all. Would you prefer the results in a single file per email or single file per filter? Given the potential number of filters that may be in a daily email, from our perspective, we would prefer a single file per email. In this file, the individual filter results would be separated by the name (and new header.)



General Discussion · What is the closest programming language to Stockfetcher?
tomb
msg #105907
4/13/2012 4:53:06 PM

Good question. The short answer, we did not base the syntax on an existing language.

The StockFetcher syntax is completely custom, and something that has "evolved" over the last 11 years. Initially, our focus was to provide easy to read, and understand, natural language constructs to build filters. Obviously, as demand has grown for more complex filtering logic and custom measures, we introduced the very basic "set{}" variable syntax.

Filter text is pre-processed and compiled into a series of events and indicators that are executed by the StockFetcher back-end. The back-end is a custom engine designed specifically to handle stock price data, allowing us to compute custom, dynamic measures on-the-fly, across a diverse collection of distributed servers.

Hope that helps a bit. If you have any additional questions, or would like further details, please let us know!

Tom
StockFetcher.com Support



General Discussion · For Stockfetcher guys
tomb
msg #105486
3/16/2012 4:08:47 PM

Hopefully we can address your issues below:

> 1) To request real time data feed by Stockfetcher. Woudl be helpful to users like me.

We do not have plans, at this time, to add real-time data to StockFetcher.

> 2) Indicators on charts to show value so for users to easily know the readings.

This is great idea. We are in the process of reworking our charts and this feature will be included.

> 3) Automate trades based on defined filters would be excellent and take away emotions and other limitations one may have.

We have no plans to add this functionality.

> 4) Have a separate section for users to make requests. Good one for Stockfetcher to know user demands and act accordingly.

We do not have plans on adding a separate section for requests. This was supported in the past; however, due to the level of information we require for requests and bug-fixes, we strongly encourage all support requests be sent to support@stockfetcher.com

Thank you,

Tom
StockFetcher.com Support

Backtesting Support · limit open
tomb
msg #105128
2/24/2012 9:22:16 AM

@Kevin_in_GA: In most cases we find that issues are much more effectively addressed and understood via email. Again, we attempt to keep up with requests via forum posts; however, we do not have a chance to respond, via the forums, to each one.

As far as the original request, please see the following help topic:

http://help.stockfetcher.com/sfhelp/?id=100389

StockFetcher.com Support


General Discussion · WISHLIST FOR STOCKFETCHER IN 2012
tomb
msg #104157
1/2/2012 10:28:39 AM

Thank you for the great feature requests -- please keep them coming!

A couple questions and comments on the items mentioned so far:

1) Concerning the weekly open problems, can you provide more details concerning the errors you are seeing with weekly open? The weekly open used by StockFetcher is the open price from the first trading date of the week.

2) With respect to Canadian data (and other markets for that matter) we have supported other markets in the past, but due to lack of interest we were unable to justify continued support for those markets. We are considering bringing additional markets back, but would like to get a general feel for how much interest there is for new markets. As well as some thoughts on desired use; for example, would you want a mix of markets or primarily interested in a single market?

Please keep the ideas/suggestions coming!

Tom
StockFetcher Support


General Discussion · A challenge to TomB and the Stockfetcher Crew
tomb
msg #95222
7/29/2010 12:04:17 PM

Also, a quick follow-up on the original request. We have created two new functions:

SfPosDiv(ind1, ind2, period, pctChg)
SfNegDiv(ind1, ind2, period, pctChg)


Note: these functions are part of a new feature that allows for custom user defined functions. In essence these functions are based on the exact code you specified.

While we do not have a release date for opening up this feature, we are hoping to allow custom user functions in the near future. You'll also notice the legends on the charts are somewhat lengthy, we hope to fix that with future updates to the user-defined functions feature.



Examples:

Fetcher[sfPosDiv(MACD Fast Line(12,26,9), MA(3), 10,3) is above 0]



Fetcher[sfNegDiv(MACD Fast Line(12,26,9), MA(3), 10,3) is above 0]



Comparing with your original:

Fetcher[/*CODING FOR DIVERGENCES*/
SET{MACD_UP, COUNT(MACD(12,26,1) GAINED MORE THAN 3% OVER THE LAST 10 DAYS,1)}
SET{MACD_DN, COUNT(MACD(12,26,1) DROPPED MORE THAN 3% OVER THE LAST 10 DAYS,1)}

SET{MA3_UP, COUNT(MA(3) GAINED MORE THAN 3% OVER THE LAST 10 DAYS,1)}
SET{MA3_DN, COUNT(MA(3) DROPPED MORE THAN 3% OVER THE LAST 10 DAYS,1)}

SET{POS_DIV, MACD_UP * MA3_DN}
SET{NEG_DIV, MACD_DN * MA3_UP}

POS_DIV is above 0
]



Fetcher[/*CODING FOR DIVERGENCES*/
SET{MACD_UP, COUNT(MACD(12,26,1) GAINED MORE THAN 3% OVER THE LAST 10 DAYS,1)}
SET{MACD_DN, COUNT(MACD(12,26,1) DROPPED MORE THAN 3% OVER THE LAST 10 DAYS,1)}

SET{MA3_UP, COUNT(MA(3) GAINED MORE THAN 3% OVER THE LAST 10 DAYS,1)}
SET{MA3_DN, COUNT(MA(3) DROPPED MORE THAN 3% OVER THE LAST 10 DAYS,1)}

SET{POS_DIV, MACD_UP * MA3_DN}
SET{NEG_DIV, MACD_DN * MA3_UP}

NEG_DIV is above 0
]




General Discussion · A challenge to TomB and the Stockfetcher Crew
tomb
msg #95217
7/29/2010 11:51:52 AM

We definitely aren't afraid to open the door to feature requests!

We'll be honest when a requested feature is something we are unable to implement or do not plan on implementing at this time. However, if it is something that we can implement and will help you and help the site, we are always willing to look into new features.

In fact, as requested here is a new correlation function:

Correlation (corr)

Below is an example that may help. Basically looks for stocks whose price was positively correlated to SPY over the last 100 days (starting 30 days ago) but have become negatively correlated within the last 30 days.

Fetcher[show stocks where corr(SPY,100,close) 30 days ago is above 0.50
and corr(SPY,30, close) is below -0.250
and close is above 3.00
and average volume(30) is above 250000
and add column corr(SPY,100,close) 30 days ago {long_corr}
and add column corr(SPY,30,close) {short_corr}
and compare with SPY
and chart-length is 100 days
]



This function deviates from your request in that only 1 symbol is specified. Obviously, you can focus the results using the "apply to symlist" and "apply to watchlist" features. You can also focus results to specific correlations using the "ind()" function. For example:

Fetcher[
set{myvar,IND(IBM,CORR(SPY,30,CLOSE))}
close is above 10
and add column myvar
]



The above will create a constant variable which is the correlation two specific equities.

Hope that helps!

Tom
StockFetcher.com Support


General Discussion · Is the newly revised Watch List finished?
tomb
msg #94996
7/22/2010 7:54:38 PM

Feel free to ask us directly! Even better, you can join the BETA testing group to check things out and send us feedback and feature suggestions.

We are still working on the final version, but tomorrow we expect to have a new BETA release for testing.

Thanks!

Tom
StockFetcher.com Support

WatchList Beta Testing · Up and down arrows
tomb
msg #94528
7/3/2010 2:40:53 PM

Hi,

To remove the arrows:

1. Click the "Edit" button near the top center of the application.
2. Select the column(s) that have arrows.
3. In the "Conditional Formatting" section to the far right, change the up and down arrows to the "empty" icon.
4. Click "Save".

Tom
StockFetcher Support


WatchList Beta Testing · Request for Report Views
tomb
msg #94510
7/2/2010 2:28:33 PM

As we continue to build the new Watch List and Reporting application, we would love to hear any suggestions for sample report "views". If you have already fired up the application, then you have likely seen a couple example "views" we have put together to help illustrate this feature.

At this point, we would like to help build some examples that provide analysis which is meaningful to you. For example, what indicators/filters do you use to help you determine if you would buy, sell, short or cover a stock? Or, what conditions do you look for to determine if a stock is reversing?

In our examples, we have used very basic filters such as:

"RSI(15) below 30" is "oversold", etc.
"MACD Fast Line crossed above MACD Slow Line" - "buy" signal.

Any suggestions you are willing to provide in this thread would be great. Once we get them, we'll start building a "community view" that puts these into action.

Also, if you prefer to keep your approaches private but would like an example, feel free to email us and we would be more than happy to help build an analysis view for you.

Thanks!

Tom
StockFetcher.com Support




StockFetcher Forums ·  · << 1 2 3 4 5 ... 27 >>

*** Disclaimer *** StockFetcher.com does not endorse or suggest any of the securities which are returned in any of the searches or filters. They are provided purely for informational and research purposes. StockFetcher.com does not recommend particular securities. StockFetcher.com, Vestyl Software, L.L.C. and involved content providers shall not be liable for any errors or delays in the content, or for any actions taken based on the content.


Copyright 2018 - Vestyl Software L.L.C.Terms of Service | License | Questions or comments? Contact Us
EOD Data sources: DDFPlus & CSI Data Quotes delayed during active market hours. Delay times are at least 15 mins for NASDAQ, 20 mins for NYSE and Amex. Delayed intraday data provided by DDFPlus


This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.