I wanted to make a 3-channel mnist digit so, since I couldn’t turn off shuffle and take three separate inputs, tried to use the same input three times with two Merge components set to concatenate
Observations & Questions
- Merge_3 shows the same pattern twice - this is correct/expected
- Merge_4 shows all three channels different - this is (very) unexpected
- Q1 - is this unexpected-to-me behaviour by design?
- I could just about expect two different patterns if input1 to Merge_4 was a different sample to inputs 1 & 2 of Merge_3 (though I’d still call that unfortunate design), but… all 3 different?
- Reshape_2 shows 3x3 multicoloured pixelated digits
- Q2 - why is it 3x3 grid? Confirm not greyscale because of the unexpected concatenation behaviour?
- Q3 - am I doing something wrong with my Merge components
- Q4 - how could I use components and this data set to create the 3-channel data I wanted for convolution experiments
Suggestion: why not allow Merge to accept as many inputs as one drags onto it for concatenation. Consider the concatenations of Inception… lots of separate components to build it, then to repeat.
Suggestion: when updating component settings, don’t update the component/model until the user has hit “Apply” (new feature I suppose); the model updates on every change, creating errors due inconsistency that is purely ephemeral (I noticed this when changing the shape of the reshape from 28x28x3 to 3x28x28 to see what happened.)
And finally, but less definitively, why is the result different when the operations are ordered differently like this