2D report with traces from multiple geometry contexts

[orlisd]

Hello everyone,

I am trying to create a single field report in Maxwell3D using the same calculator expression on multiple polylines (geometry context) but none of my approaches work. Can anybody comment on what I am missing?
Thanks!

# ...
# m3d = Maxwell3D(...) # I'm using 24R2
# any design with an expression "B_rad" that can be calculated on a polyline should work to use this script
polylines = [
    "SampleLine_01",
    "SampleLine_02",
    "SampleLine_03",
    "SampleLine_04"] #polyline names in the design

# Option 1
# doesn't work as intended
report1 = m3d.post.create_report(
    plot_name="B_rad for all polylines - option 1",
    report_category="Fields",
    expressions=["B_rad"]*len(polylines),
    context=polylines   # -> doesn't work cause it expects a string
    # context=polylines[0] # -> this would add 4x B_rad plots for the [0] context
)

# Option 2
# doesn't work. Adds traces from Design Category (e.g. Volume(object)) instead
report = m3d.post.create_report(
    plot_name="B_rad for all polylines - option 2",
    report_category="Fields"
)
for line in polylines:
    report.polyline = line
    report.add_trace_to_report(
            traces=["B_rad"],
            context=[line]
    )

# Option 3
# Works, creating many plots which is not intended
for line in polylines:
    report3 = m3d.post.create_report(
        plot_name="B_rad for all polylines option 3",
        report_category="Fields",
        expressions=["B_rad"],
        context=line
    )

[jvela018]

Hi @orlisd ,

It seems that the ways you're attempting to plot don't work because of misuse of the create_report method. Note that for instance in Case 1, the context takes a str, as specified in the documentation:

Furthermore, the polyline is an object, and what you need is the name. In your case, you've created a list of polyline objects. You maybe just swap your current definition to look something like:

# Modified Option 3
for line in polylines:
    report3 = m3d.post.create_report(
        plot_name="B_rad for all polylines modified option 3",
        report_category="Fields",
        expressions=["B_rad"],
        context=line.name
    )

In the modified Option 3, I'm addressing all the issues you saw in the previous two options, the context is a string that refers to the poly line from the polylines list you're looping through.

For more information about how to use this method: https://aedt.docs.pyansys.com/version/stable/API/_autosummary/ansys.aedt.core.modules.solve_setup.Setup.create_report.html

Please, if this works for you mark it as correct answer so that it pops up to anyone else experiencing a similar issue.

/jvela018

[orlisd]

Dear jvela018,

Thanks for revisiting this. Your reply and suggestion, however, is wrong.

Your modification of my code in option 3 uses line.name to (correctly) provide a str to the context, but the line variable used in the loop is already a string. Therefore, your code directly returns and AttributeError ('str' object has no attribute 'name').

I include a screenshot below to help clarify the issue.

• Top left you see the model with four of the polylines used (SampleLine01...04)
• "B_rad for all polylines option 3", 4, 5, 6 show the plots created with the "option 3" I have provided.
• "Calculator Expressions Plot 1" shows the goal plot, using all different contexts (Polylines) in the same plot.

Since submitting this question, I have identified another solution, which seems aligned with the UI given that a 2D report can only be created for a given context. Therefore, to use more contexts, one should first create the report and then add additional traces. In this case, add_trace_to_report expects a list for context

report4 = m3d.post.create_report(
        plot_name="B_rad for all polylines option4",
        report_category="Fields",
        expressions=["B_rad"],
        context=polylines[0],
        polyline_points=501
    )
for line in polylines[1:]:
    report4.add_trace_to_report(
        # traces=["B_rad"],
        traces=[],
        context=["Context:=",line]
    )

Nevertheless, add_trace_to_report seems to be doing something weird in this case and adds more traces than needed. Specifically, in this example, polylines[1] is added one time, polylines[2] is added two times, and polylines[3] is added four times. It's like the Y-Component of the trace info is appended on each call. This is a bit deeper in (py)AEDT code and diverges from the topic in this question (I believe it's worth investigating though, seems like a bug to me).

On this topic, I can accept the fact that create_report is not intended to use more than a single context.
Thanks.