search

pointwise / CaeUnsAzore

The Pointwise CAE Export Plugin for AzoreCFD
Other
0 stars 0 forks source link

how to use its API to determine whether it is structured grid or unstructured grid #1

Open songqinghao opened 2 years ago

songqinghao commented 2 years ago

Hello, when using SDK to develop pointwise plugin, how to use its API to determine whether it is structured grid or unstructured grid (I only want to deal with unstructured grid, so I need to determine), I don't see this aspect of knowledge in the official website of a write documentation and examples, hope to understand it, thanks.

dbgarlisch commented 2 years ago

See How to Create a Plugin, Additional Reference Materials, and Implement the Plugin

Are you building a plugin Exporter or Importer?

For an Exporter, you must specify structured or unstructured using the -caeu or -caes option to mkplugin. A plugin exporter can only support one or the other. A plugin cannot export a mixed structured and unstructured mesh.

For an Importer, you have to look at the file being imported to determine which zones are structured or unstructured. A plugin Importer can import a mixed mesh. You just need to use different API calls.

See apiGridModel.h File Reference

For further expert help, you can contact Fidelity Pointwise Support.

[PluginSDK-v0100r16]$ ./mkplugin -h

usage:

  mkplugin.tcl [-h] [-v] [-f] [-noprefix] -caes|-caeu|-grdp -c|-cpp PluginName

where,

  -caes
      Creates a CAE exporter project that supports structured grids.
      Name prefix is 'CaeStr'.

  -caeu
      Creates a CAE exporter project that supports unstructured grids.
      Name prefix is 'CaeUns'.

  -grdp
      Creates a grid importer project. Name prefix is 'Grdp'.

  -c
      Use procedural C api in the plugin. This is the only option
      supported by -grdp at this time.

  -cpp
      Use object oriented C++ api in the plugin. This option cannot
      be used with -grdp (yet).

  -noprefix
      If present, PluginName is used as-is *without* applying the
      standard name prefix.

  -h
      Displays this usage.

  -v
      Displays verbose runtime information.

  -f
      Forces over-write of an existing plugin.

  PluginName
      Specifies the plugin's base name. PluginName will be prefixed
      with CaeUns, CaeStr, or Grdp accordingly (see -noprefix).

If mkplugin is successful, the plugin's source folder will be located
in './src/plugins/[Prefix]PluginName/'.

FYI...
    tcl version '8.5'...
songqinghao commented 2 years ago

Thanks for your answer, I know what to do next.