Marco Antonio Barroca

Hey, I will likely need this feature in the near-ish future. Would you guys mind if I tried adding it to the `JordanWignerMapper`myself?

Was this implementation working previously? @BStar14 [@GyeonghumKim](https://github.com/GyeonghunKim) @0sophy1 I was going through it and updating it to work with the recent updates. Mostly this means using PauliSparseOp and converting the...

I've modified the implementation to use the FermionicOp arithmetic instead of doing so only at the end. Seems simpler this way and I've recovered the same results from the original...

Found the issue! Both implementations work fine! Just do a `print(second_q_op.normal_order()-reverse_op.normal_order())` and you'll see they match up to e-17! ``` Fermionic Operator number spin orbitals=4, number terms=14 0j * (...

Done! I think reverse JordanWigner will be enough for what I’m working on but I wonder if there shouldn’t be a ReverseQubitMapper() or modify/rename FermionicMapper() class in the future to...

I'm interested in this as well. I have had some issues with VQE calculations returning "Internal server errors" and it would be good to have the job retry a few...

I've been messing around trying to see if I can solve this. I tried creating a custom Estimator that is a child class of the runtime Estimator and inserts retries...

Didn't see you had an implementation already! Will try it out!

Python script to reproduce the issue ``` from qiskit.algorithms import VQE, NumPyMinimumEigensolver, NumPyEigensolver #Algorithms #Qiskit odds and ends from qiskit.circuit.library import EfficientSU2, EvolvedOperatorAnsatz from qiskit.algorithms.optimizers import COBYLA, SPSA, SLSQP, L_BFGS_B...

Is it okay to mark this as a feature request? This seems like a useful feature to have in the future.