-
Some parts of the interface are super slow. Like the queue page. The rest call returns the song IDs, at which point the interface has to make n more calls for each song in the queue to get more info…
-
Thanks for the package! I'm trying to use it in my study with a sample size around 26,000 (10 covariates). However, in the following paper:
Messy Data, Robust Inference? Navigating Obstacles to Inf…
-
The current repo organisation is very messy and needs better re-organisation. Below are notes
- All examples should be implemented in both Turing.jl and Stan.jl
- Each of them needs a file for m…
-
Many emitters send messages multiple times for redundancy. Often there is no protocol-level support and the 3 or 4 bursts are really one logical transmission. While e.g. receiving the temperature t…
-
Hey Matt,
https://clipperhouse.github.io is perfect for a kV store like boltdb.
The time consuming messy aspects of a kV store is when you need to do lots of transformations on top with an open curso…
ghost updated
8 years ago
-
### Prerequisites
- [X] I have searched for similar features requests in both open and closed tickets and cannot find a duplicate.
- [X] The feature is still missing in the latest stable version o…
-
Hi!
It would be very useful to have a data source that outputted the outgoing IPs for the public runners. This would be useful when whitelisting access to resources based on IP (Yes, I know this i…
-
This package does a very good job of helping the editors get a grasp on what's usually just "the _SEO_ stuff" to them. We'd really like to provide the info in the editors' native language though, so t…
-
Also mark properties that change their values when crawling,
like file-paths or URLs to source files, which might change from a repo-relative path
to a URL with a fixed commit hash in it.
This mi…
-
It could be helpful to include more instruction on how to clean geospatial data. The data used in the notebooks has been carefully curated and is very clean. However, raw data is often full of errors,…