milktrader
milktrader
The `readable` method would solve this issue as well as make the code for `Quandl` a lot neater (and reliable given the trouble with missing values). Currently, `readable` does not...
Have you tracked down what's going on?
Check to make sure your changes were properly merged, I needed to resolve conflicts and believe I preserved your fixes @LeoK987
`@require` from the Requires package
maybe dispatch `quandl` as a symbol? `search(:quandl, "GDP USA", results=30)`
Or probably more elegant to just use `quandl(s::String)` for get and `quandl(s::String, n::Int)` for search?
Here is the `quandlget` dispatch: ````julia function quandlget(id::AbstractString; order="des", rows=100, frequency="daily", transformation="none", from="", to="", format="TimeArray", api_key="", silent=false) ```` If we change kwargs to parameters (i.e., get rid of the `;`)...
I am happy to grant access to developers within this organization. I agree it's best to consolidate our efforts here. Please advise what projects, packages or groups you're interested in....
@dysonance can you elaborate what features in `xts` you'd like to see in `TimeSeries`. I'm very familiar with `xts` and authored `TimeSeries`. I'm also open to a new time series...
[Hierarchy of Packages](https://github.com/JuliaQuant/Roadmap/issues/3) this is over two years old but there is a Roadmap for JuliaQuant that would be a good place to continue this discussion.