Skip to content

Possible extensions of total_size #2125

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
pwl opened this issue May 4, 2017 · 1 comment
Closed

Possible extensions of total_size #2125

pwl opened this issue May 4, 2017 · 1 comment
Assignees

Comments

@pwl
Copy link

pwl commented May 4, 2017

I have some trouble understanding the total_size parameter and there is no mention of it in the docs. From the examples I have seen so far the parameter should be set to the total size of the training data when doing mini-batch training. This is simple to interpret if the data is just a 1d array but what should I put in there if I'm training a model on views of 2d data (subsampling in both dimensions)? Should I then use total_size=data.shape[0]*data.shape[1]?

From the gitter conversation it seems that total_size for subsampling in more then 1 dimensions needs some extra support on the pymc3 side. @ferrine suggested the following API:

total_size = int # for shape[0] subsampling
total_size = [int, None, int] # for subsampling [shape[0], shape[2]]
total_size = [int, Ellipsis, int] # for subsampling [shape[0], shape[-1]]

In my 2d case I would write total_size = [data.shape[0], data.shape[1]].

@junpenglao
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants