Error message for Correlation not very helpful.
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- julia
- Domain
- machine-learning
Research direction
Start by reproducing the shown MXNet.jl Correlation call with the two reshaped arrays, then trace the Correlation implementation and the source of the reported dimension check. Done means determining whether the input or settings are invalid and, if this is an error-reporting issue, documenting the expected explanation or a clearer failure.
Written by the indexing model from the issue text.
Description
It may be just me, but I'm trying to learn MXNet.jl by doing, given that I can't find many examples around. I have the following code
a = [1 2 3 4;
4 3 2 1]
b = [4 3 2 1;
1 2 3 4]
mx.Correlation(mx.NDArray(reshape(a, (1,1,2,4))), mx.NDArray(reshape(b, (1,1,2,4))))
that gives me this error:
Check failed: top_width_ >= 1U (0 vs. 1) Correlation cannot be done with current settings.Neighborhood and kernel don't fit in blob
I tried looking for that in the source code, but I struggle to extrapolate what that condition means. Can anyone shed some light on this?
- Dominant language
- No language data
- Stars
- 370
- Forks
- 63
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dmlc/MXNet.jl
-
Import fail MXNET.jlOpen
Difficulty 3/5 1-2 days Newbie friendliness 28/100
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Segfault running MNIST example lenet-stn.jlPossibly taken @iblislin claimed this 3241 days ago. Openupstream
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
UKGovernmentBEIS/optstop#10 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
aws-samples/sample-per-model-bedrock#546 ·
Maintainers usually reply within 1 day
-
nn::linear: weight initialization depends on `bias` because the bias is created before the weightPossibly taken @monfortema claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
LaurentMazare/tch-rs#1067 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
low AI-generated score
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
UKGovernmentBEIS/inspect_evals#2765 ·
Maintainers usually reply within 1 day