Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Capacitance body is not defined in Elmer rendering "add_solution_setup('capacitance')" #1008

Open
vegaonline opened this issue Dec 31, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@vegaonline
Copy link

Information

  • Qiskit Metal version: 0.1.5
  • Python version: 3.11.11
  • Operating system: Ubuntu 22.04 kernel 6.8.0-50-generic

What is the current behavior?

For Elmer Rendering, rendering, meshing, gui launching is done without error while elmer_renderer.add_solution_setup('capacitance') tells
(1) Capacitance body is not defined,
(2) No attribute "nets".

`

AttributeError Traceback (most recent call last)
Cell In[16], line 2
1 # Add a solution to solve for Capacitance matrix
----> 2 elmerRenderer.add_solution_setup('capacitance')

File ~/WORK/QC/qiskit-metal/qiskit_metal/renderers/renderer_elmer/elmer_renderer.py:537, in QElmerRenderer.add_solution_setup(self, sim_name, solver_names, equation_name)
534 bodies = self.define_bodies(setup, eqn, materials)
536 # Add boundary conditions
--> 537 boundaries, cap_body = self.define_boundaries()
539 if cap_body == 1:
540 self.logger.warning(
541 "WARNING: No capacitance bodies added to the model other "
542 "than those connected to ground. ElmerFEM cannot run a "
543 "capacitance extraction analysis without any bodies. ")

File ~/WORK/QC/qiskit-metal/qiskit_metal/renderers/renderer_elmer/elmer_renderer.py:619, in QElmerRenderer.define_boundaries(self)
615 continue
617 phys_grps_dict.update(ph_geoms)
--> 619 for net, geom_names in self.nets.items():
620 geom_id_list = [
621 phys_grps_dict[f"{name}_sfs"] for name in geom_names
622 ]
624 if net == "gnd":

AttributeError: 'QElmerRenderer' object has no attribute 'nets'
`

However, elmer_renderer.py has assign_nets().

I also wish to mention that Analyze_a_transmon_using_ElmerFEM.py works smoothly without any error.

Steps to reproduce the problem

What is the expected behavior?

It is expected to run that line without error.
Screenshot from 2024-12-31 11-53-56

Suggested solutions

@vegaonline vegaonline added the bug Something isn't working label Dec 31, 2024
@zlatko-minev
Copy link
Collaborator

Can you try it with the #1002 pull request and let @shanto268 there know if you still see it

@vegaonline
Copy link
Author

vegaonline commented Dec 31, 2024

Thanks.
@zlatko-minev and @shanto268, I installed pyside6 and tested. I am still getting those errors. The issue creeps in here

`AttributeError Traceback (most recent call last)
Cell In[20], line 2
1 # Add a solution to solve for Capacitance matrix
----> 2 elmerRenderer.add_solution_setup('capacitance')

File ~/WORK/QC/qiskit-metal/qiskit_metal/renderers/renderer_elmer/elmer_renderer.py:537, in QElmerRenderer.add_solution_setup(self, sim_name, solver_names, equation_name)
534 bodies = self.define_bodies(setup, eqn, materials)
536 # Add boundary conditions
--> 537 boundaries, cap_body = self.define_boundaries()
539 if cap_body == 1:
540 self.logger.warning(
541 "WARNING: No capacitance bodies added to the model other "
542 "than those connected to ground. ElmerFEM cannot run a "
543 "capacitance extraction analysis without any bodies. ")

File ~/WORK/QC/qiskit-metal/qiskit_metal/renderers/renderer_elmer/elmer_renderer.py:619, in QElmerRenderer.define_boundaries(self)
615 continue
617 phys_grps_dict.update(ph_geoms)
--> 619 for net, geom_names in self.nets.items():
620 geom_id_list = [
621 phys_grps_dict[f"{name}_sfs"] for name in geom_names
622 ]
624 if net == "gnd":

AttributeError: 'QElmerRenderer' object has no attribute 'nets' `

Wish ALL of YOU a Happy and Prosperous NEW YEAR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants