Quality of life

In this merge request I propose multiple changes which should improve the usage of the Python API of Aidge:

New Features:

• Add a set_attr method to StaticAttribute objects
• Add a set_attr method to DynamicAttribute objects
• Add magic method __set_attr__ & __get_attr__ to StaticAttribute

Allow the use of

dilation_dims = conv.DilationDims  # __get_attr__ example
conv.DilationDims = [2, 2]         # __set_attr__ example

• Add magic method __set_attr__ & __get_attr__ to DynamicAttribute
• Add **kwargs to GeneriOp ctor to declare more easily attributes:

Usage example

test_op = aidge_core.GenericOperator(
        "Test_generic",
        1,
        0,
        1,
        name="test_op",
        attribute_1=1,
        attribute_2=True,
        attribute_3=0.001
    )

• Allow Numpy->Tensor conversion with no available Backends (move TensorImpl backend_cpu to core)
• Allow to specify a Backend to choose for Numpy->Tensor conversion

assigned to @cmoineau

changed target branch from main to dev

@pineapple I let you change Milestone if you want ! I have set target branch to be dev.

changed milestone to %aidge_core - v0.2.0

added LanguagePyBind PriorityMedium StatusWork in Progress labels

Very good idea! I think we should have an entire Epic dedicated to user interface with subjects such as:

• access / set attributes
• Connector to link Nodes
• intuitive training process
• accessing Tensor values for Operators in the middle of a GraphView (pretty uneasy for now)
• setting backend, datatype, data format

• Connector we already have, maybe a refactor can be done but we will need to specify what we want
• I want to do a global variable to set a default backend/datatype/dataformat what do you think ? I think it will make things easier.

What is a Tensor without a Backend?

n = np.zeros(shape=(4,5))
t = aidge_core.Tensor(n)

Where are datza stored in this case?

added 1 commit

• f28a09ed - [PyBind] Add support for setAttrPy for Dynamic and Static Attributes.

Compare with previous version

marked the checklist item Add a set_attr method to StaticAttribute objects as completed

changed the description

added 1 commit

• 76e8a21d - Add __setattr__ and __getattr__ methods for Attributes. This recquired a...

Compare with previous version

76e8a21d introduces an "annoying" change.

Due to Python MRO, I needed to change the order of declaration of derived class to implement __setattr__ and __getattr__ methods.

See the related pybind issue : https://github.com/pybind/pybind11/issues/3804

I added this specification to the wiki: https://gitlab.eclipse.org/groups/eclipse/aidge/-/wikis/Python%20binding

I have just got a false hope ...

Looking at the PyBind doc, since 2.6 a tag prepend have been introduce to push a function to the top of the overload chain.

But it looks like that __setattr__ and __getattr__ are treated specially and are hard coded as pointed out by this pybind issue...

So at the moment, we will still have to keep declaring Attributes before OperatorTensor which I find annoying.

marked the checklist item Add magic method __set_attr__ & __get_attr__ to StaticAttribute as completed

marked the checklist item Add magic method __set_attr__ & __get_attr__ to DynamicAttribute as completed

added 1 commit

• d68006ec - [PyBind] Update GenericOp ctor to use kwargs to set attributes.

Compare with previous version

added 1 commit

• 5686ecb8 - Add unittest for magic method setter and attribute set by kwargs.

Compare with previous version

marked the checklist item Add **kwargs to GeneriOp ctor to declare more easily attributes: as completed

added 1 commit

• e9c566d1 - Renamed pybind_Parameter.cpp -> pybind_Attributes.cpp to reflect name change.

Compare with previous version

With the changes made to Attribute, I am realizing that manipulating them is hard has we lack documentation on them.

A solution I propose to add to this MR is to create a static method getAttributesName() which will return a list of all the availables Attribute for an object.

This method will provide the user a quick check on what attribute he can call but it will also allow to automatically add to the documentation the Attributes available for an object.

This is possible using a Jinja template just as in : https://gitlab.eclipse.org/eclipse/aidge/aidge/-/blob/master/docs/conf.py?ref_type=heads#L96-102

@pineapple @olivierbichler ?

added 1 commit

• 175657a0 - Fix warning issue kw_only.

Compare with previous version