A new command to get the maximum qubits supported by a target

[Avhijit-Nair]

Please describe what you would like the feature to accomplish.
A new function call that can programmatically return the maximum number of qubits supported by a simulator or a real hardware available in Azure Quantum workspace.

Describe the solution you'd like
A command such as ionq.simulator.get_max_qubits() that will return the max qubits associated with the particular simulator. for example, the above command should return 29 since the limit of IonQ simulator is 29.

Describe alternatives you've considered
As of now the only way to do the above said task is to hard code the value according to the specifications of the target.

Additional context
Nothing as of now.

[danielstocker]

Hi @Avhijit-codeboy

Thanks for your suggestion. I am a program manager for the Azure Quantum service. @bettinaheim has handed this GitHub issue over to me after a quick internal discussion as this isn't something that we can address in the runtime.

I will discuss the feature request with our internal teams and keep you up to date here. In future if you would like to reach the Service team directly and for the quickest response you can raise feature requests and questions that relate to the Azure Quantum service here: https://docs.microsoft.com/en-us/answers/topics/azure-quantum.html

I will update you on Monday (5/17) on the progress of my internal discussions.

[Avhijit-Nair]

Hi @danielstocker !

Thanks a lot for taking up the issue with your internal teams. Looking forward to having this feature in future.

[danielstocker]

Hi @Avhijit-codeboy - I've got an update on our internal discussions today.

First of all thanks again for raising the request. I shared the Azure Q&A link above and our community support team reminded me that the place for product feedback is actually still https://feedback.azure.com - We'll move to a new system in future but should be able to carry asks across.

With that out of the way let me update you on your ask.

• We reviewed this with our team and are evaluating how we might support this feature in the future.
• We now have this on our backlog and continuously prioritize work items based on customer feedback like your post here.
• We are always looking for ways to improve resource estimation capabilities in Azure Quantum. (like the capability suggested) Your feedback is truly important here and we appreciate it.

cc: @bromeg

[Avhijit-Nair]

@danielstocker that sounds cool! I put up a new feature suggestion here - https://docs.microsoft.com/en-us/answers/topics/azure-quantum.html, but I'll put it up again at https://feedback.azure.com.

The feature suggestion is related to getting the maximum number of shots allowed on a particular hardware available in Azure Quantum workspace. Something like ionq.qpu.get_max_shots() might do the job.

This feature can help developers prevent attacks such DoS or raise any other error that breaches the limit.

[danielstocker]

@Avhijit-codeboy No need to repost on feedback.azure.com :) I'm already looking at that other post and am hoping to get back to you early next week over on Azure Q&A after we've considered this one