{"sections":[{"heading":"Before starting","paragraphs":["Field plots help inspect how a model distributes a selected electromagnetic quantity in space. They supplement the extracted circuit result; the colour plot alone does not establish convergence or physical accuracy. This worked example requests magnetic flux density B on a plane above the strip and current density J on the conductors.","Download the complete field-example ZIP or save the three complete files below together in a new writable folder. Use matching licensed InductEx/TTH tools. The recorded CLI is InductEx 8.0.1 with TTH 1.1.50, and the native controls were exercised in the current Windows source candidate. This teaching process is not a calibrated fabrication stack."]},{"heading":"Define the field request and sampling plane","paragraphs":["Plot [B, J] belongs inside the IXI COMMAND record. FPLANE is outside STRUCT: its corner and translation coordinates are in metres even though the process uses Units = 1e-6. The supplied plane runs from x = -5 to 105 micrometres and y = -10 to 20 micrometres, translated to z = 2 micrometres. Keep each coordinate triple on its own line.","FieldMeshSize = 5 uses the process length unit and controls this plane sampling. SegmentSize = 2 still controls the cuboid conductor mesh. Changing field sampling, changing the conductor mesh and changing arrow density are different operations. The checked generated request applies the plane to B; J is written on conductor geometry, not on the B sampling plane."]},{"code":"inductex strip.ixi","figures":[{"asset_id":"studio-field-b-heatmap","caption":"Actual B-plane vector-magnitude view for 10.000GHz_p1_imag. The native view reports 293 finite three-component tuples. The quantity label follows the known generated B output; retain its request and runtime identity."}],"heading":"Generate and open the current output","steps":["Open strip.ixi in Studio, save the complete inputs and use the normal extraction action. For the optional CLI route, run the command below from the folder containing all three files.","Check the current completion verdict and diagnostics. This example generates output/B_strip.vtk and output/J_strip.vtk, along with the model mesh and numerical results. The unchanged extracted L1 remains 3.89648e-12 H at GUI precision.","Open B_strip.vtk through File > Open or the project artifacts. In Fields, select the required array and choose Apply field view. Keep the full array name visible when recording or comparing a view.","The checked files contain 10.000GHz_p1_imag and 10.000GHz_p2_imag. Next array selects the other excitation and wraps back. These are the arrays actually emitted by this run; do not assume that every requested file contains both real and imaginary arrays."]},{"figures":[{"asset_id":"studio-field-b-arrows","caption":"Actual directional-arrow view with Medium display density. The selected array and its data range remain the same as the heatmap."},{"asset_id":"studio-field-b-streamlines","caption":"Actual plane streamlines with High density. These follow the tangential projection of the selected imaginary array; they do not show a combined complex field."}],"heading":"Choose the quantity and display","paragraphs":["Use Component to choose vector magnitude or a signed X, Y or Z component. The checked Z component crosses zero; its colour range has both negative and positive values. Magnitude is computed from the selected real or imaginary vector array. It is not the combined complex AC amplitude and is not a time animation.","Heatmap colours the selected quantity on the supplied geometry. Directional arrows show the full vector direction, while streamlines on a plane follow its tangential projection. A vector normal to the plane can therefore have arrows without an in-plane streamline. These traces describe sampled spatial data, not moving particles or an additional field solve.","Density and Arrow size control readability. In the checked view, Low, Medium and High density increased generated arrow geometry while the B array retained the same 293 tuples. A larger arrow size changed the display extent without changing its tuple count. Increasing those settings does not refine the solver mesh or add field samples."]},{"figures":[{"asset_id":"studio-field-invalid-range","caption":"The invalid 0.05 minimum is visible beside maximum 0.04. The diagnostic explains the rejection, while the legend retains the valid 0 to 0.04 range."}],"heading":"Set a useful range and recover an invalid value","paragraphs":["Auto range uses the selected data. For a controlled comparison, use the same quantity/component and explicit manual endpoints in both views; independently auto-ranging two plots can make unlike magnitudes look similar. For this B magnitude, 0 to 0.04 T is a valid illustrative manual range. It is a display choice, not an accuracy tolerance.","Manual endpoints must be finite and minimum must be less than maximum. The checked change from minimum 0 to 0.05, while maximum remained 0.04, produced a diagnostic and retained the last valid 0 to 0.04 payload. Correcting minimum to 0 recovered the manual view; choosing auto range recovered its original data-derived endpoints. Read the active range and message rather than assuming that every typed value was applied. The exact diagnostic is: Manual field range min must be less than max."]},{"heading":"Keep field and model coordinate scales consistent","paragraphs":["Leave Show model mesh off for this checked example. Enabling it appends the adjacent strip.msh to the metre-valued field geometry without a compatible scale conversion in the current candidate (KB-GUI-010). The combined payload width becomes about 110 instead of 0.00011, so this overlay is not accepted as an aligned model context.","Disabling the option restores the field-only bounds and range. Keep the original output files; do not rewrite their coordinates merely to obtain a plausible picture. The candidate needs a validated coordinate-system relationship before the grey model context can be relied on for this route. A nearby filename alone does not establish equal units."]},{"figures":[{"asset_id":"studio-field-j-heatmap","caption":"Actual generated J vector-magnitude view. Its conductor data has 14301 tuples, compared with 293 samples on the separate B plane."}],"heading":"Inspect current density and save the view","paragraphs":["Open J_strip.vtk and apply the intended array in Fields. The checked J file contains 14301 finite three-component tuples for each of its two excitation arrays. This is conductor current density output, with generated J units of A/m2; it is distinct from the B plane.","Use Solid to return to ordinary geometry and Apply field view to restore the selected field. The checked route recovered the same B array, range and bounds after this change. Export snapshot writes the current field canvas and a companion report; review the report for private paths before sharing it. The dedicated snapshot guide explains save cancellation and failure/retry."]},{"heading":"Check output identity before interpreting values","paragraphs":["Keep the saved request, solver version, generated filename, complete array name, quantity and coordinate scale together. The checked B VTK has a misleading free-text title saying Electric current density generated by TTH (KB-OUTPUT-001). Its generated request explicitly routes B to B_strip.vtk, and Studio labels that known filename as B in Tesla. Neither a generic title nor a renamed file prefix is sufficient authority for an arbitrary output.","The CLI and native runs emitted identical parsed vector arrays. Studio magnitude and signed-component endpoints agreed with those values within the stated binary32 display-representation allowance. This checks data/display consistency, not an independent physical field reference or convergence criterion.","If a file is missing, start with the current run diagnostic, requested Plot values and the supported mode/engine. If the view seems empty, check the selected array, component, range and model-overlay state before changing the physical calculation. Cancellation, field-view state after restart, other VTK formats and final distributed-package acceptance still require their own checks."]},{"code":"* Parameterised inline equivalent of the maintained microstrip geometry\n$COMMAND\n  MeshFile \"strip.msh\"\n  MeshType CUBE\n  Mode MQS\n  Plot [B, J]\n  Netlist \"strip.cir\"\n  Process \"process.ldf\"\n$END\n$VARIABLE\n  Name strip_length\n  Value 100\n$END\n$VARIABLE\n  Name strip_width\n  Value 10\n$END\n$STRUCT\n  Name inline_strip\n  $POLY\n    Layer M1\n    XY\n    (0,0)\n    (0,%strip_width)\n    (%strip_length,%strip_width)\n    (%strip_length,0)\n    (0,0)\n  $END\n  $PATH\n    Layer TERM\n    Width 1\n    XY\n    (0,%strip_width)\n    (0,0)\n  $END\n  $PATH\n    Layer TERM\n    Width 1\n    XY\n    (%strip_length,%strip_width)\n    (%strip_length,0)\n  $END\n  $TEXT\n    Text \"P1 M1 M0\"\n    Layer TEXT\n    XY\n    (0,%strip_width/2)\n  $END\n  $TEXT\n    Text \"P2 M1 M0\"\n    Layer TEXT\n    XY\n    (%strip_length,%strip_width/2)\n  $END\n$END\n\n$FPLANE\n  Coords\n  (-5e-6,-10e-6,0)\n  (105e-6,20e-6,0)\n  Translate\n  (0,0,2e-6)\n$END","heading":"Complete strip.ixi"},{"code":"* Public microstrip teaching stack; dimensions use Units below\n$Parameters\n  Units = 1e-6\n  SegmentSize = 2.0\n  FieldMeshSize = 5.0\n  AbsMin = 0.025\n  GPOverhang = 5.0\n  ProcessHasGroundPlane = TRUE\n  GPLayer = 17\n  TermLayer = 19\n  TextLayer = 18\n  HFilaments = 1\n  TerminalInRange = 1.0\n  UnitL = 1\n$End\n$Layer\n  Number = 17\n  Name = M0\n  Thickness = 0.2\n  Lambda = 0.09\n  Order = 0\n  Mask = -1\n  Filmtype = S\n  HFilaments = 2\n$End\n$Layer\n  Number = 2\n  Name = I0\n  Thickness = 0.15\n  Order = 1\n  Mask = -1\n  Filmtype = I\n$End\n$Layer\n  Number = 5\n  Name = M1\n  Thickness = 0.25\n  Lambda = 0.09\n  Order = 2\n  Mask = 1\n  Filmtype = S\n  HFilaments = 3\n$End","heading":"Complete process.ldf"},{"code":"* Extraction topology, design inductance in henries because UnitL=1\nL1 1 2 3.9e-12\nP1 1 0\nP2 2 0\n.end","heading":"Complete strip.cir"}],"canonical_url":"https://www.sun-magnetics.com/knowledge-base/inductex-field-plots","url":"/knowledge-base/inductex-field-plots","known_issues":[{"disposition":"verified_workaround","id":"KB-GUI-010","title":"Field model context combines incompatible coordinate scales","public_notice":"Leave Show model mesh off for this generated field example because the overlay combines incompatible coordinate scales. The checked field-only view does not qualify the overlay or field accuracy.","claim_scope":"Only the affected claim and recorded build/input; not whole-guide or final-release acceptance"},{"disposition":"supported_path","id":"KB-OUTPUT-001","title":"B output carries a current-density VTK title","public_notice":"Keep the B/J request, runtime, excitation and file identity with each field. The generic VTK title or filename alone is not sufficient quantity or unit authority.","claim_scope":"Only the affected claim and recorded build/input; not whole-guide or final-release acceptance"}],"search_record":{"execution":true,"relatedProducts":[],"version_tags":["InductEx 8 preview"],"text":"Generate and inspect magnetic field and current density plots Request B and J from a complete MQS strip, inspect the emitted excitation arrays in Studio and choose field displays and ranges with their coordinate and metadata limits explicit. InductEx Windows InductEx 8.0.1 / TTH 1.1.50 and Studio source candidate; final-package review pending How to magnetic field current density field plot Plot B J FPlane FieldMeshSize VTK Apply field view imaginary array manual range Show model mesh field disappears coordinate scale Before starting Field plots help inspect how a model distributes a selected electromagnetic quantity in space. They supplement the extracted circuit result; the colour plot alone does not establish convergence or physical accuracy. This worked example requests magnetic flux density B on a plane above the strip and current density J on the conductors. Download the complete field-example ZIP or save the three complete files below together in a new writable folder. Use matching licensed InductEx/TTH tools. The recorded CLI is InductEx 8.0.1 with TTH 1.1.50, and the native controls were exercised in the current Windows source candidate. This teaching process is not a calibrated fabrication stack.  Define the field request and sampling plane Plot [B, J] belongs inside the IXI COMMAND record. FPLANE is outside STRUCT: its corner and translation coordinates are in metres even though the process uses Units = 1e-6. The supplied plane runs from x = -5 to 105 micrometres and y = -10 to 20 micrometres, translated to z = 2 micrometres. Keep each coordinate triple on its own line. FieldMeshSize = 5 uses the process length unit and controls this plane sampling. SegmentSize = 2 still controls the cuboid conductor mesh. Changing field sampling, changing the conductor mesh and changing arrow density are different operations. The checked generated request applies the plane to B; J is written on conductor geometry, not on the B sampling plane.  Generate and open the current output Open strip.ixi in Studio, save the complete inputs and use the normal extraction action. For the optional CLI route, run the command below from the folder containing all three files. Check the current completion verdict and diagnostics. This example generates output/B_strip.vtk and output/J_strip.vtk, along with the model mesh and numerical results. The unchanged extracted L1 remains 3.89648e-12 H at GUI precision. Open B_strip.vtk through File > Open or the project artifacts. In Fields, select the required array and choose Apply field view. Keep the full array name visible when recording or comparing a view. The checked files contain 10.000GHz_p1_imag and 10.000GHz_p2_imag. Next array selects the other excitation and wraps back. These are the arrays actually emitted by this run; do not assume that every requested file contains both real and imaginary arrays. inductex strip.ixi Actual B-plane vector-magnitude view for 10.000GHz_p1_imag. The native view reports 293 finite three-component tuples. The quantity label follows the known generated B output; retain its request and runtime identity. The actual B plane heatmap displays the selected 10.000GHz_p1_imag vector magnitude, 293 finite tuples and generated B units in Studio. Choose the quantity and display Use Component to choose vector magnitude or a signed X, Y or Z component. The checked Z component crosses zero; its colour range has both negative and positive values. Magnitude is computed from the selected real or imaginary vector array. It is not the combined complex AC amplitude and is not a time animation. Heatmap colours the selected quantity on the supplied geometry. Directional arrows show the full vector direction, while streamlines on a plane follow its tangential projection. A vector normal to the plane can therefore have arrows without an in-plane streamline. These traces describe sampled spatial data, not moving particles or an additional field solve. Density and Arrow size control readability. In the checked view, Low, Medium and High density increased generated arrow geometry while the B array retained the same 293 tuples. A larger arrow size changed the display extent without changing its tuple count. Increasing those settings does not refine the solver mesh or add field samples.  Actual directional-arrow view with Medium display density. The selected array and its data range remain the same as the heatmap. Directional arrows show the selected B array with Medium density and arrow size; colour follows vector magnitude. Actual plane streamlines with High density. These follow the tangential projection of the selected imaginary array; they do not show a combined complex field. The selected B array is shown as plane streamlines with High density; these are spatial traces of the tangential field projection. Set a useful range and recover an invalid value Auto range uses the selected data. For a controlled comparison, use the same quantity/component and explicit manual endpoints in both views; independently auto-ranging two plots can make unlike magnitudes look similar. For this B magnitude, 0 to 0.04 T is a valid illustrative manual range. It is a display choice, not an accuracy tolerance. Manual endpoints must be finite and minimum must be less than maximum. The checked change from minimum 0 to 0.05, while maximum remained 0.04, produced a diagnostic and retained the last valid 0 to 0.04 payload. Correcting minimum to 0 recovered the manual view; choosing auto range recovered its original data-derived endpoints. Read the active range and message rather than assuming that every typed value was applied. The exact diagnostic is: Manual field range min must be less than max.  The invalid 0.05 minimum is visible beside maximum 0.04. The diagnostic explains the rejection, while the legend retains the valid 0 to 0.04 range. Manual minimum 0.05 exceeds maximum 0.04; Studio reports the error and retains the previous valid 0 to 0.04 field colour range. Keep field and model coordinate scales consistent Leave Show model mesh off for this checked example. Enabling it appends the adjacent strip.msh to the metre-valued field geometry without a compatible scale conversion in the current candidate (KB-GUI-010). The combined payload width becomes about 110 instead of 0.00011, so this overlay is not accepted as an aligned model context. Disabling the option restores the field-only bounds and range. Keep the original output files; do not rewrite their coordinates merely to obtain a plausible picture. The candidate needs a validated coordinate-system relationship before the grey model context can be relied on for this route. A nearby filename alone does not establish equal units.  Inspect current density and save the view Open J_strip.vtk and apply the intended array in Fields. The checked J file contains 14301 finite three-component tuples for each of its two excitation arrays. This is conductor current density output, with generated J units of A/m2; it is distinct from the B plane. Use Solid to return to ordinary geometry and Apply field view to restore the selected field. The checked route recovered the same B array, range and bounds after this change. Export snapshot writes the current field canvas and a companion report; review the report for private paths before sharing it. The dedicated snapshot guide explains save cancellation and failure/retry.  Actual generated J vector-magnitude view. Its conductor data has 14301 tuples, compared with 293 samples on the separate B plane. The actual J output shows the selected current density vector magnitude with 14301 finite tuples and generated A per square metre units. Check output identity before interpreting values Keep the saved request, solver version, generated filename, complete array name, quantity and coordinate scale together. The checked B VTK has a misleading free-text title saying Electric current density generated by TTH (KB-OUTPUT-001). Its generated request explicitly routes B to B_strip.vtk, and Studio labels that known filename as B in Tesla. Neither a generic title nor a renamed file prefix is sufficient authority for an arbitrary output. The CLI and native runs emitted identical parsed vector arrays. Studio magnitude and signed-component endpoints agreed with those values within the stated binary32 display-representation allowance. This checks data/display consistency, not an independent physical field reference or convergence criterion. If a file is missing, start with the current run diagnostic, requested Plot values and the supported mode/engine. If the view seems empty, check the selected array, component, range and model-overlay state before changing the physical calculation. Cancellation, field-view state after restart, other VTK formats and final distributed-package acceptance still require their own checks.  Complete strip.ixi * Parameterised inline equivalent of the maintained microstrip geometry\n$COMMAND\n  MeshFile \"strip.msh\"\n  MeshType CUBE\n  Mode MQS\n  Plot [B, J]\n  Netlist \"strip.cir\"\n  Process \"process.ldf\"\n$END\n$VARIABLE\n  Name strip_length\n  Value 100\n$END\n$VARIABLE\n  Name strip_width\n  Value 10\n$END\n$STRUCT\n  Name inline_strip\n  $POLY\n    Layer M1\n    XY\n    (0,0)\n    (0,%strip_width)\n    (%strip_length,%strip_width)\n    (%strip_length,0)\n    (0,0)\n  $END\n  $PATH\n    Layer TERM\n    Width 1\n    XY\n    (0,%strip_width)\n    (0,0)\n  $END\n  $PATH\n    Layer TERM\n    Width 1\n    XY\n    (%strip_length,%strip_width)\n    (%strip_length,0)\n  $END\n  $TEXT\n    Text \"P1 M1 M0\"\n    Layer TEXT\n    XY\n    (0,%strip_width/2)\n  $END\n  $TEXT\n    Text \"P2 M1 M0\"\n    Layer TEXT\n    XY\n    (%strip_length,%strip_width/2)\n  $END\n$END\n\n$FPLANE\n  Coords\n  (-5e-6,-10e-6,0)\n  (105e-6,20e-6,0)\n  Translate\n  (0,0,2e-6)\n$END Complete process.ldf * Public microstrip teaching stack; dimensions use Units below\n$Parameters\n  Units = 1e-6\n  SegmentSize = 2.0\n  FieldMeshSize = 5.0\n  AbsMin = 0.025\n  GPOverhang = 5.0\n  ProcessHasGroundPlane = TRUE\n  GPLayer = 17\n  TermLayer = 19\n  TextLayer = 18\n  HFilaments = 1\n  TerminalInRange = 1.0\n  UnitL = 1\n$End\n$Layer\n  Number = 17\n  Name = M0\n  Thickness = 0.2\n  Lambda = 0.09\n  Order = 0\n  Mask = -1\n  Filmtype = S\n  HFilaments = 2\n$End\n$Layer\n  Number = 2\n  Name = I0\n  Thickness = 0.15\n  Order = 1\n  Mask = -1\n  Filmtype = I\n$End\n$Layer\n  Number = 5\n  Name = M1\n  Thickness = 0.25\n  Lambda = 0.09\n  Order = 2\n  Mask = 1\n  Filmtype = S\n  HFilaments = 3\n$End Complete strip.cir * Extraction topology, design inductance in henries because UnitL=1\nL1 1 2 3.9e-12\nP1 1 0\nP2 2 0\n.end","id":"inductex-field-plots","keywords":"magnetic field current density field plot Plot B J FPlane FieldMeshSize VTK Apply field view imaginary array manual range Show model mesh field disappears coordinate scale","kind":"How to","title":"Generate and inspect magnetic field and current density plots","product":"InductEx"},"version":"Windows InductEx 8.0.1 / TTH 1.1.50 and Studio source candidate; final-package review pending","id":"inductex-field-plots","related":["/knowledge-base/inductex-inspect-mesh-fields","/knowledge-base/inductex-mesh-snapshot","/knowledge-base/inductex-staged-run","/knowledge-base/inductex-mesh-size-cost"],"downloads":[{"url":"/_functions/kbExample?name=inductex-mqs-field-strip.zip","scope":"Exact checked input files plus instructions; final-release/platform applicability remains pending.","files":["strip.ixi","process.ldf","strip.cir","README.txt"],"id":"inductex-mqs-field-strip","requires":["Matching licensed InductEx 8/TTH runtime","New writable folder; keep all three input files together","Keep Show model mesh off for KB-GUI-010; retain known request/file identity for KB-OUTPUT-001","Review the stated Windows scope; physical field accuracy and final-package acceptance remain pending"],"title":"Complete MQS B-plane and J strip inputs"}],"publication_status":"published","numerical_output":null,"provenance":{"execution_checks":[{"routes":["cli","gui-native-scenario"],"scope":"Fresh licensed CLI and normal native B-plane/J generation; exact emitted arrays, displayed magnitude/signed component ranges, array switching, arrows/streamlines/density/size, manual-range rejection/recovery, Solid/reapply and actual snapshot export","result":"passed","articles":["inductex-field-plots","inductex-inspect-mesh-fields"],"purpose":"generated-mqs-fields-native-controls-and-recovery","version":"Windows catalog CLI 8.0.1/TTH 1.1.50 and frozen native Studio/Core source candidate, 3 November 2026","id":"VAL-027","records":["normal licensed CLI field pilot","fresh native source run with B and J outputs","independent parsed VTK comparison","field payloads before/after controls","actual PNG/report export","actual browser ZIP download and four independent fresh replay checks"],"limit":"Twenty-eight checks distinguish generated-data/display representation from numerical field accuracy. The B free-text VTK title is misleading (KB-OUTPUT-001), and the adjacent model overlay mixes coordinate scales (KB-GUI-010); overlay alignment is not accepted. Physical pickers, field cancellation/restart, all formats, independent physical field/convergence reference and final-package/full-article acceptance remain pending. EQS is excluded.","observed":{"J_magnitude_range":[279882100,3300867000000],"arrays":["10.000GHz_p1_imag","10.000GHz_p2_imag"],"B_point_count":293,"field_only_width":0.000109999999040156,"B_magnitude_range":[0.0005062921641488311,0.029787774932525508],"representation_allowance":"Four binary32 ULPs for conversion/norm display mapping only, not physical field accuracy.","metadata_issue":"KB-OUTPUT-001","J_point_count":14301,"model_issue":"KB-GUI-010","plane_z_m":0.000002,"with_model_width":110.00000333786,"model_overlay_accepted":false}}],"figure_evidence":[{"evidence_limit":"Illustrates the selected emitted array and stated display only. No model-overlay alignment, complex-amplitude interpretation, physical field accuracy or complete release acceptance is inferred. KB-GUI-010 and KB-OUTPUT-001 remain open.","id":"studio-field-b-heatmap","reference_label":"Frozen Windows Studio source candidate, actual generated MQS fields, 3 November 2026"},{"evidence_limit":"Illustrates the selected emitted array and stated display only. No model-overlay alignment, complex-amplitude interpretation, physical field accuracy or complete release acceptance is inferred. KB-GUI-010 and KB-OUTPUT-001 remain open.","id":"studio-field-b-arrows","reference_label":"Frozen Windows Studio source candidate, actual generated MQS fields, 3 November 2026"},{"evidence_limit":"Illustrates the selected emitted array and stated display only. No model-overlay alignment, complex-amplitude interpretation, physical field accuracy or complete release acceptance is inferred. KB-GUI-010 and KB-OUTPUT-001 remain open.","id":"studio-field-b-streamlines","reference_label":"Frozen Windows Studio source candidate, actual generated MQS fields, 3 November 2026"},{"evidence_limit":"Illustrates the selected emitted array and stated display only. No model-overlay alignment, complex-amplitude interpretation, physical field accuracy or complete release acceptance is inferred. KB-GUI-010 and KB-OUTPUT-001 remain open.","id":"studio-field-invalid-range","reference_label":"Frozen Windows Studio source candidate, actual generated MQS fields, 3 November 2026"},{"evidence_limit":"Illustrates the selected emitted array and stated display only. No model-overlay alignment, complex-amplitude interpretation, physical field accuracy or complete release acceptance is inferred. KB-GUI-010 and KB-OUTPUT-001 remain open.","id":"studio-field-j-heatmap","reference_label":"Frozen Windows Studio source candidate, actual generated MQS fields, 3 November 2026"}],"review_notes":["Twenty-eight checks cover separate CLI generation and normal native controls. Native rendering and a finite array do not establish physical field accuracy. Twenty-eight checks distinguish generated-data/display representation from numerical field accuracy. The B free-text VTK title is misleading (KB-OUTPUT-001), and the adjacent model overlay mixes coordinate scales (KB-GUI-010); overlay alignment is not accepted. Physical pickers, field cancellation/restart, all formats, independent physical field/convergence reference and final-package/full-article acceptance remain pending. EQS is excluded.","The Field Plotting reference still matches its inventoried SHA-256. Its examples/fields statement has not been established as applicable to the current catalog package; this guide supplies its complete checked input ZIP."],"scope":"Recorded inputs/builds only. Complete walkthrough and final-package acceptance remain separate.","verification_requirements":{"gui_method":"product-native scenario or recorded operator walkthrough; relevant screenshots required","status":"review-incomplete","illustrations":"required","required":["technical-review","release-applicability","execution","recovery","numerical-interpretation","gui-workflow","illustrations"],"legacy_walkthrough_field":"pending retained; full article/release acceptance remains open"},"sources":[{"id":"inductex:docs/manual/ix_fieldplot.tex","section":"Plot requests, FPlane sampling, legacy VTK and field-display interpretation"},{"id":"inductex:docs/manual/ix_layoutinput.tex","section":"FPlane outside STRUCT uses metre coordinates"},{"id":"inductex:docs/manual/ix_ldf.tex","section":"Units and FieldMeshSize"},{"id":"inductex:docs/manual/studio_results.tex","section":"Fields controls, ranges and snapshots"},{"id":"validation:inductex-fields-windows-20261103","section":"VAL-027; twenty-eight generation/display checks; overlay and metadata findings retained"}]},"title":"Generate and inspect magnetic field and current density plots","type":"How to","markdown_url":"/_functions/kbResource?path=markdown%2Finductex-field-plots.md","summary":"Request B and J from a complete MQS strip, inspect the emitted excitation arrays in Studio and choose field displays and ranges with their coordinate and metadata limits explicit.","product":"InductEx"}