Also new to QuantConnect, getting a bit lost...

Hey Fred! Sorry about the issues you are having, I'm afraid most of them sound like your internet connection, or no javascript permissions. Everything is working well (debug, backtesting, building). Safari had issues for a while which we fixed a few weeks ago. We can't support older versions of Safari. Intraday charting hasn't been done yet but its definitely on the list :) Indicators are trickier to use: I'd recommend starting with the open source documentation (https://lean.quantconnect.com/docs#topic14.html). If you have any suggestions to make them easier we'd welcome them! Its requires implementing 2 methods (IsReady, ComputeNextValue). There are many 20+ examples of indicators here: https://github.com/QuantConnect/Lean/tree/master/Indicators

Try to also clearing browser's cache as if you use long periods with minimal resolutions, browser would slow down considerably (even Chrome).

Wow, fast replies... I didn't really expect anything today ;) A few notes on both replies: The site was feeling a bit sluggish this morning, so that may be related. I'd be surprised if it was just a matter of clearing the cache or using the latest version of Safari. I now switched to Chrome, so this is the latest version, brand new with no prior data. Anyway, I'll try on another connection as soon as possible, clearing all previous data from the browser, just in case... On the matter of different timeframes, I wasn't really talking about charting (even if that helps debugging, and visualizing, of course), but at the very least for backtesting. Right now it looks like one has to implement a 'consolidator' to create the bars at the desired timeframe, and I have no idea whatsoever how indicators would work in this case. But indeed, the open source documentation seems to be a bit more complete on some matters. I'll try going on with that from now on. However, still no clue on to how to make the Debug method work... Thanks for the help!

We pre-consolidated data into ticks, seconds and minutes. Any further you'd need to do yourself but its fairly simple. Its a class called "Consolidator" which you create and update. When its ready it fires an event with the consolidated bar. I'll ask Michael to post an example today - he built this system. The Debug is working well, just clone the basic template to test. If you're not seeing debug messages it probably because that part of your code isn't running. If you send multiple identical messages the system ignores them to prevent you crashing your web browser.

Yeah, I saw the consolidator code, but I was wondering how it was behaving with regards to the registering of indicators where you have to specify a resolution. Obviously custom resolutions wouldn't exist there. I managed to get the debug logging working, but only from the QCAlgorithm subclass. Apparently, it will refuse to work from any Indicator subclass, which would be most helpful when trying to implement an indicator.

Hey Fred! There's a lot of things going on here so I'll try to respond to each one. I was curious as to your C# experience level. This will help in future posts so I can point you to relevant resources. Debug function You mention errors getting the 'Debug' function work and saying you're getting errors that it is 'not found'. Does your code compile? If it doesn't compile I imagine you're trying to call the Debug function from a place that doesn't have the Debug function. The Debug function is defined on the QCAlgorithm class, so you have to call it on that class. See the MSDN documentation for more information on method invocation. Custom indicator implementation This would be easier to help you with if you were able to share some code. We have a tutorial in the documentation on how to create your own indicator. As Jared stated, you should only need to derive from the base class and implement a couple functions. Indicators are never concerned with the resolution of data they receive (by design) so you shouldn't need to update your indicator when you want to change your resolution, you would just send different data to it. I also suggest looking at the many implementations that are a part of the core product. If you have trouble creating an indicator, please share your algorithm and I'll help you get it working. That's what I'm here for!! Online terminal It sounds like a spotty connection, but if the online IDE isn't ideal for you, then I would recommend coding your algorithms in Visual Studio C# Express Edition. It's free and awesome. You can fork the github repository and run locally, debugger step through and everything! Then when you have something working, copy the files into QC and run on more data. Changing resolutions This should be easy if you design your algorithm with this in mind. Take a peak at this example I recently posted. It gives a pattern for creating lots of indicators against lots of symbols. It may be a little more advanced (I'm not sure of your C# level), but I think it showcases that changing the resolution of data for a consolidator is as simple as changing the value of a single field (in this case BarPeriod). Indicators with consolidators Consolidators are a wonderful way to provide automatic updates for your various indicators. Have a look at the documentation for consolidators. In short, we allow for consolidators to be registered through a call to the SubscriptionManager.AddConsolidator. This registers the consolidator to receive automatic updates for the requested symbol. The consolidator fires events to let listeners know that it has consolidated a new piece of data. We can wire these events up to update our indicator. This is how the helper functions cause automatic updates for indicators. I'd recommend browsing around the examples in the github repository and trying to edit them. If you have problems trying to accomplish something, please share your algorithm and I'll be more than happy to help you get it working! Let me know if there's any other questions I can answer for you.

Thanks for the reply to the different questions. I'll investigate consolidators and timeframes more thoroughly a bit later, and also grab the code for the indicator and post it here to have your opinion on it. I finally managed to get it to work, but I'm not sure this is the right way to go, and I found quite a few weird things in the process. However, a few notes on the points you mention: - I have no experience in C#, but I'm an experienced Obj-C developer, so switching between languages is usually not a problem - Nice to know the 'Debug' method is defined in QCAlgorithm. I finally figured that out by trial and error. But this would be an important thing to state in the documentation. The documentation just described it as a "helper function" and gives its prototype. Usually a helper function is something that is defined globally. The documentation should state that this is part of QCAlgorithm. - And unfortunately, the online terminal is the only solution for me, as I won't be running Visual Studio anytime soon on OS X...

Actually,. I'm also started to get such strange errors of backtest window not appearing (status also not updating). Cache clearing doesn't help here.

@Tadas - In the results view, you can see the "Waiting Time" -- 99.9% of the time this should be 0-minutes. You won't ever have to wait to run a backtest. But if people are sending too many they queue up and you might need to wait a little. This morning there was someone issued lots of parallel, 2+ hour backtests which chewed up the whole cloud :)

Yes, I mean it doesn't load when actually it is already done or with runtime error. Backtest is shown "in queue" for very long, then I just refresh window and it's sitting there (results or error). But I think it's all caused by overload, so I can just wait.