Draft: Feat/operator_unsqueeze

Context

See issue : aidge_core#65 (closed)

I think for operators only requiring data reorganization, a default implementation could be provided in the core, relying on Tensor copy functionnalities...

I'm ok with that.

If I understand well there would not be any UnsqueezeImpl_cpu_forward_kernel function, just a copy of tensor in the Aidge::UnsqueezeImpl_cpu::forward()?

Actually, there would not even be any implementation at all in CPU backend.

I might be out of ideas on how to implement that. How would the forward function be called then ? I might need some real life guidance from you or @pineapple tomorrow.

I am applying the same principle for the Reshape operator right now. You will be able to take it as an example in the MR aidge_core!104 (merged) probably tomorrow when I will be able to push it!

Please have a look at my MR, I just pushed changes for example for operator Reshape.

I have put the Unsqueeze_OpImpl in core in the mr : aidge_core!102 (closed)

added 1 commit

• c2dcfd1c - feat : forward function now relies on the tensorImpl->copy function

Compare with previous version

closed

This is just formatting

reopened

added 1 commit

• 4f27bc62 - chore : removed debug var

Compare with previous version

added 5 commits

• 4f27bc62...76ed60c4 - 4 commits from branch eclipse/aidge:dev
• 2399f0c7 - Merge branch 'dev' of...

Compare with previous version

marked this merge request as draft

added 1 commit

• b35a6f08 - chore : removed the unsqueeze operator to move it in aidge_core, also commented teest temporarly

Compare with previous version

added 1 commit

• 0c1b23e7 - feat : added MANIFEST.in

Compare with previous version

added 1 commit

• 5720b19f - chore : moved test to aidge core

Compare with previous version

added 1 commit

• 1e16a792 - chore : deleted MANIFEST.in, this file is meant to go in another branch

Compare with previous version