You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we just return all loaded objects from JSON files without modification. JSON3 generates Objects, which are AbstractDict{Symbol}s but can also be accessed with string indices and a dot syntax. We may want to reformat these outputs for better compatibility with Julia. For example:
We want to make sure that loaded reference posterior draws implement the Tables interface. The eltype of the vector of draws should be the narrowest possible eltype. The idea is to make it straightforward for users to analyze the draws, e.g. by plotting them.
Since posteriordb is very Stan-focused (only contains one pymc model) and will for now likely be used in conjunction with the StanJulia packages, a useful check would be that we can use all model code and data directly in StanSample.jl.
The text was updated successfully, but these errors were encountered:
I propose we format all JSON outputs to be AbstractDict{String}s, as these still implement the Tables interface. We may also want to use OrderedCollections.OrderedDict to store the outputs, as this preserves the ordering in case that is important, and OrderedCollections is a light and common dependency.
Currently, we just return all loaded objects from JSON files without modification. JSON3 generates
Object
s, which areAbstractDict{Symbol}
s but can also be accessed with string indices and a dot syntax. We may want to reformat these outputs for better compatibility with Julia. For example:Since posteriordb is very Stan-focused (only contains one pymc model) and will for now likely be used in conjunction with the StanJulia packages, a useful check would be that we can use all model code and data directly in StanSample.jl.
The text was updated successfully, but these errors were encountered: