Registration decorator for parametric pulse shapes

What is the expected behavior?

From @eggerdj on PR #3463 which introduces Parametric Pulses:

Is there some way around this structure? I’m thinking of the following scenario: External party, named ABC, wants to use Qiskit and provide their own pulse shapes. It would be a lot nicer if, a user of ABC, in his application, could do

from ABC.parametric_pulses import ABCPulse

where ABC.parametric_pulses.py contains the parametric pulses defined by ABC, without having to manually register the parametric pulse names in this Enum class. Is something like that possible?

The goal of this feature is to replace manually entering new parametric pulses into the mapper in assemble.

[drewrisinger]

@jwoehr, I don’t think so. Pulse Builder still doesn’t cover e.g. a linear ramp parametric pulse defined as e.g. y = m*t + b. I’ve been using my workaround to add this functionality.

[jwoehr]

@jwoehr, I don’t think so. Pulse Builder still doesn’t cover e.g. a linear ramp parametric pulse defined as e.g. y = m*t + b. I’ve been using my workaround to add this functionality.

Thank you, noting that, @drewrisinger