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

ROADMAP: Standard configuration file #5517

Open
Samuelopez-ansys opened this issue Dec 3, 2024 · 1 comment
Open

ROADMAP: Standard configuration file #5517

Samuelopez-ansys opened this issue Dec 3, 2024 · 1 comment
Milestone

Comments

@Samuelopez-ansys
Copy link
Member

Creating a standard and human-readable configuration file for PyAEDT to store and load settings

@Samuelopez-ansys Samuelopez-ansys converted this from a draft issue Dec 3, 2024
@Samuelopez-ansys Samuelopez-ansys added this to the v2.0 milestone Dec 3, 2024
@SMoraisAnsys
Copy link
Collaborator

SMoraisAnsys commented Dec 3, 2024

@Samuelopez-ansys If it makes sense, that's what I had in mind

flowchart LR

subgraph NC[" "]
    direction TB
    A[Native CAD 
    with history and parametrization]
end

subgraph SD["Source Data"]
  direction LR
  MAS
  MCAD["Motor CAD"]
  CAD
  PCBLayout["PCB Layout"]
  BOM
  MA["Mesh Assembly"]
  3DB["3D Blocs"]
  Netlist
end

subgraph SM["Simulation Model"]
  direction LR
  Geometry
  MatA["Material Assignment"]
  SS["Simulation Setup"]
  subgraph SMsub0[" "]
    direction LR
      Boundaries
      Sources
      MS["Mesh Settings"]
  end
  subgraph SMsub1[" "]
    direction LR
      RS("Report Setup")
      VC("Virtual Compliance")
      FPP("Field Post-Processing")
  end
end

NC -->|Geometry Service| SD
SD -->|Configuration File| SM

classDef blue fill:lightblue, fill-opacity:0.5, stroke:lightblue
class Geometry,MatA,SS,SMsub0,SMsub1 blue
classDef orange fill:orange, fill-opacity:0.5, stroke:orange  
class Boundaries,Sources,MS,RS,VS,VC,FPP orange

Loading

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Q2 2025 - Apr-Jun
Development

No branches or pull requests

2 participants