All Things Ansys 106: Fluent Updates in Ansys 2022 R1


Published on: February 25th, 2022
With: Eric Miller & Sina Ghods

In this episode your host and Co-Founder of PADT, Eric Miller is joined by PADT’s senior application & support engineer Sina Ghods for a look at what’s new for Fluent in the first Ansys release of 2022.

If you want to learn more about this update, view PADT’s webinar on the topic here:

If you have any questions, comments, or would like to suggest a topic for the next episode, shoot us an email at we would love to hear from you!



Mechanical Updates in Ansys 2022 R1 pt. 1 – General Advancements & Composites – Webinar

With the comprehensive suite of structural analysis simulation tools that Ansys provides, engineers can simulate everything from impact & penetration, to heat transfer and much more. With a wide range of applications and product integrations, Ansys structural analysis helps to solve the toughest product challenges. Potentially the most impactful tool in this product family is Ansys Mechanical – the best-in-class finite element solver. 

Mechanical enables users to solve complex structural engineering problems and make better, faster design decisions, and nowhere has this been more true than in Ansys 2022 R1. When looking at this latest release, it is clear that a lot of time and effort went into crafting the best possible tool for increased accessibility and helping users succeed. 

Join PADT’s Senior Mechanical Engineer and mechanical expert Joe Woodward for our first look at what is new in Ansys 2022 R1, focusing on general advancements and composites updates.

This presentation will include enhancements made for: 

  • File management
  • Seam welding
  • Importing geometry
  • Plot visualization
  • And much more

Register Here

If this is your first time registering for one of our Bright Talk webinars, simply click the link and fill out the attached form. We promise that the information you provide will only be shared with those promoting the event (PADT).

You will only have to do this once! For all future webinars, you can simply click the link, add the reminder to your calendar and you’re good to go!

Setting Up and Using Ansys Elastic Licensing

It’s 2022, and if you don’t cringe and remember a Tiktok trend when you hear the word elastic, consider yourself lucky (or just old.)

[Editor’s note: don’t google it, now I have a very stupid song stuck in my head]

In the past couple of years, the license masters at ANSYS introduced Elastic Licensing. After multiple iterations, they settled on a model where customers can purchase blocks of “License Hours” that unlock a large block of the ANSYS tools and software.

The typical use cases for elastic licensing are for customers that need to:

  1. Utilize several different ANSYS tools but not enough to justify purchasing/leasing separate licenses for the different products.
  2. Accommodate larger jobs or burst solves that require a large/r number of cores or licenses.
  3. A need to utilize ANSYS tools sparsely or on project basis.
  4. Smaller operations or startups that have budget constraints but need access to world class tools to grow.
  5. Consulting companies that directly bill to customers or against specific contracts/charge numbers.

If you have any questions or are interested in exploring the different costs & options please contact your ANSYS account manager.

What I am interested in sharing today is more on the setup and usage side of Elastic Licensing.

Elastic Licensing is supported starting in version 2019 R2, requires an active internet connection and some minor configurations on the ANSYS client computers.

The first step once the Elastic license entitlements are delivered is to log in to the ANSYS licensing portal at Under the “Elastic Licensing” menu on the left side, both active and inactive entitlements can be viewed. Make sure the elastic entitlements are present and are active.

The next step is to acquire the elastic server ID and set an elastic PIN number. This can be done under the Elastic Credentials menu item further down the page. The server ID and PIN are required to identify the elastic account that clients will be drawing from, and the PIN is to ensure that only authorized users have access to the ANSYS Elastic Currency. Users can either note the ID and PIN down or export the ID & PIN in a .json file.

To configure a workstation to utilize Elastic licensing, the steps are:

  1. Login to ANSYS Licensing portal
  2. Click on Elastic Credentials
  3. Either click “Export ID & PIN” or note down the Elastic License Server ID and PIN
  4. In the start menu, Right Click on “ANSYS 20##.R#” > “ANSYS Client License Settings 20##.R#” and select run as administrator.
  5. Click on “Elastic Licensing” on the left
  6. Check the “Enable Elastic Licensing” box
  7. Either import ID & PIN from step 3 or type them in.
  8. Click “save” and that should be it.

For ANSYS Electronics products and for the non-graphical instances, the same elastic license server configuration can be achieved by adding the following line to the license specification file:


The license configuration file for ANSYS Electronics products can be found in C:\Program files\ansysEM\shared files\licensing\ansyslmd.ini

For non-ANSYS Electronics products, it can be found in C:\Program files\Ansys Inc\shared files\licensing\ansyslmd.ini

The line should be added immediately following the existing lines in that file.

How to verify what licenses are being utilized?

The easiest method of checking Elastic licensing usage and consumption is to check the licensing portal for consumption. The only issue there is that it takes some time for the dashboard to update.

The other -more crude- method is to check the contents of the license logs on the client machine. This is an immediate indicator on Elastic licensing success or failure and is not a consumption reporting tool.

To check the logs:

  1. Open a file explorer window and type “%temp%\.ansys\”
  2. Look for the log file named: ansyscl.HOSTNAME.log
  3. At the bottom of that text file you should see entries showing the latest license checkout.
2022/02/03 12:46:12    CHECKOUT            electronics_desktop             21.1 (2020.1029)            1/1/1/16                 1/1/1/1   11664:11664:ANSYSEDT.EXE:licenseserver:winx64                              64:

Finally, as usual, if you have any questions or run into any issues, the fastest recourse is to reach out to your ANSYS channel partner or PADT Inc at .

Fluent Updates & Advancements in Ansys 2022 R1 – Webinar

Accelerate your design cycle with the powerful fluid simulation software that is Ansys Fluent. This tool contains the best-in class physics models and can accurately and efficiently solve large, complex models. With Fluent, you can trust your simulation results with a software that has been extensively validated across a wide range of applications.

Create advanced physics models and analyze a variety of fluids phenomena—all in a customizable and intuitive space.

Join PADT’s Senior Simulation Support & Application Engineer, and Fluent expert Sina Ghods for an exploration of the latest updates and advancements available to users of Ansys Fluent in 2022.

This presentation covers the updates made to the following:

  • Electronic Cooling Analysis
  • Acoustics
  • Steady-state CFD
  • Direct Fourier Transformation (DFT)
  • And much more

Register Here

If this is your first time registering for one of our Bright Talk webinars, simply click the link and fill out the attached form. We promise that the information you provide will only be shared with those promoting the event (PADT).

You will only have to do this once! For all future webinars, you can simply click the link, add the reminder to your calendar and you’re good to go!

All Things Ansys 105: Ansys in the News – 2/7/2022


Published on: February 7th, 2022
With: Eric Miller

In this episode your host and Co-Founder of PADT, Eric Miller discusses some recent news within the world of Ansys, including a recent partnership with Amazon Web Services (AWS), Quantum Computing for Simulation, Advancements in Optics Simulation, and much more.

If you have any questions, comments, or would like to suggest a topic for the next episode, shoot us an email at we would love to hear from you!



Reading values from Excel component into Flownex Scripts!

Today we’re going to explore how we can directly reference specific cells in Excel workbooks via script. By building the direct reference in the script we can avoid having to assign specific cells as outputs and we can also avoid having to use data transfer links which can clutter our work canvas.

Code Snippets

Depending on when we want the script to execute we should choose the appropriate function to make this part of. Since I want this to be called every cycle I will make this part of the “Execute” function.

//script main execution function - called every cycle
public override void Execute(double Time)
//new code to go here	

The first bit of code we’re going to use will link our script to the excel file “Workbook (2).xlsx” in the Flownex project directory.

SpreadsheetGear.IWorkbookSet workbookSet = SpreadsheetGear.Factory.GetWorkbookSet(); 

// Path to where Flownex Project is located
System.IO.DirectoryInfo projectpath = new System.IO.DirectoryInfo(Project.ProjectRootPath);	        
// Create Workbook object linked to .xlsx file or .csv
SpreadsheetGear.IWorkbook workbook = workbookSet.Workbooks.Open(projectpath + "\\Tasks\\ExcelWorkBooks\\Workbook (2).xlsx"); 

Now that we’ve created our workbook object connected to the Excel file we can read in values from cells in a couple of different ways.

To read from an explicit cell (A1),

// Read from Cell A1 in Sheet 1
double excel_value_1 = Convert.ToDouble(workbook.Worksheets["Sheet1"].Cells["A1"].Value); 

to read from a set row and column,

// Read from Row 4, Column 1 in Sheet 2 (Note: row and column indices start at 0)
double excel_value_2 = Convert.ToDouble(workbook.Worksheets["Sheet2"].Cells[3,0].Value); 

If the value in the Excel cell is a string we can use the following,

// Read text from Cell B1 in Sheet 1
string excel_value_3 = workbook.Worksheets["Sheet1"].Cells["B1"].Value as string; 

There we have it! These are now internal variables to the script. To assign them as output variables we can use the following syntax (this is all still within the Execute function).

//Save Value to Output Script Variable
Output1.Value = excel_value_1;
Output2.Value = excel_value_2;
Output3.Value = excel_value_3;

Then, as per the usual, we’ll need a bit of code to initialize these output variables and make them visible/usable outside of the script.

//constructer initializes parameters
	public Script()
		_Output1 = new IPS.Properties.Double();
		_Output2 = new IPS.Properties.Double();
		_Output3 = new IPS.Properties.Text();

	//property declarations to make
	//parameters visible to outside world
	public IPS.Properties.Double Output1
			return _Output1;
	public IPS.Properties.Double Output2
			return _Output2;
	public IPS.Properties.Text Output3
			return _Output3;

Happy Friday and Happy Scripting!

Hold my Beer: Spatially Varying Materials in Ansys Mechanical Made Easy

Do you hear that sound? It’s the celebration of all my adoring fans celebrating a long-awaited blog post! I figured having “create new blog content” on my quarterly review for the past 32 quarters was impressive, but 33 was just unacceptable. So here we are. In an attempt to trick myself into routinely writing something, I’m starting what I’m calling “hold my beer” type of articles where a quick write-up of a work-around, fix, new feature, etc is discussed. Basically, if someone says some task is too difficult, tedious, etc… hold my beer, cuz I’mma fix that for you. 

All right, first topic… can you create a spatially varying material property definition. I sure hope you’re not using a stand-up desk… because the answer is yes. This process is more commonly used for lattice optimization (validating the variable field map), simulating composites (creating a map of degradation factors), or the newer short fiber composite workflow (which is extremely cool…check it out…caution:  potential foreshadowing). Behind the scenes, we accomplish this by using field variables. While I listed some common/standard field variables above, you’re more than welcome to define your own variable for use in mapping. These field variables are usable for most common material properties…to show I’m not lying, here’s a documentation link:

The way these field variables work is I define my material properties (see documentation above for supported materials) vs. a field variable. I then map that field variable onto my elements, and they then look up what the material is. Brilliant! 

Because I just had an MRI, let’s start with a hypothetical situation where I want to run a simulation where I’m converting MRI data into linear elastic behavior. The first stop on our journey is Engineering Data:

Note, in order for ‘field variables’ to show up I actually have to click on the material model in the outline row.  If I hadn’t clicked on ‘isotropic elasticity’ then I wouldn’t see ‘field variables’.  For this I’ll just double click ‘create field variable’:

The name here doesn’t need to match.  I’m doing that just for my own sanity.  Ultimately we’re just mapping information from a point cloud to the mesh.  After I hit ‘ok’ in that image I’ll now see:

So now I can define two dvalue lines, which could then have different temperature-dependent effects, and fill out the young’s modulus definition:

So I’ve now defined for dvalue=100, E=2E11 prxy=.3 and for dvalue=200, E=1E11 prxy=.27. 

Super easy so far. I have defined a material model that will create a tabular representation modulus. Now we go to External Data to read in a CSV file which will map the field variable onto my mesh. The benefit here is that I can mesh my model however I like, and it’ll still perform the map. 

Note that external data can map many different things.  Because we are mapping material information we need to connect it to the ‘model’ cell.  Otherwise, if we had spatially dependent boundary conditions we could link it to the setup. 

Going into External Data:

Select that to then browse to the CSV file (oh, forgot to say you need to save that excel file as a CSV):

I now need to set some controls for how the file is read (bottom-left corner) and what the columns mean (top-right) which will generate a preview (10-rows only, bottom right). 

First select the ‘material field data’ which allows you to access the field data present in Engineering Data.  Then specify the length (I took all my measurements in inches).  Then, specify your column headers to be x/y/z/dvalue.  Then verify that everything looks right in the preview…and finally toggle the option to start the import at line 2 (we don’t want to read the CSV header as mappable data). 

All done, update things on the project page and open Mechanical (note, you can do this after you’ve already built a model, as shown I’m building it from scratch…just drag/drop the connections and ensure that everything is properly updated on the project page):

Now in Mechanical, I’ll see an ‘imported material fields’ item:

Scope the material field object to the body you want, right-mouse on it and update (this will mesh the body and perform the map):

Reason it isn’t showing 100-200?  This is mapped to the elements while the keypoint measurements were on the nodes (I built the CSV by just copying the x/y/z location of all my keypoints to excel and then defining a variation in the y-direction).  So elements on the boundary will have a gradient and not be at 100 or 200…so this is correct. 

Next, you want to look at the mapped values…which is easy!  Insert a material plot into the plot branch, tada:

Lines up with the engineering data definition!

Behind the scenes you can dig into the input file to see what actually happened:

You can see lines 12581-12585 specify a tabular representation of isotropic elasticity. Then starting at line 12599 it’s starts applying a custom field variable to my elements using options from the initial-state/INISTATE family of commands. You don’t need to know any of this, I’m just showing how the sausage is made. 

So, no need to cut your model up into a bunch of slices, fight carpal tunnel defining multiple material models and assigning them down your sliced up model, then threatening to quit when someone says that the spatial variations have changed. Field variables, external data, done. 

I’ll take my beer back…

Simulation Best Practices for Heat Exchanger Design & Development – Webinar

Used in a variety of settings across a range of scales, heat exchangers must perform reliably, often in harsh conditions, and be durable enough to operate effectively despite extremes of cyclical thermal loading—sometimes for years without replacement.

Simulation offers a critical tool to optimize heat exchange performance, select the most appropriate materials, and predict durability and life. Ansys heat exchanger simulation application capabilities provide that reliability, helping users to optimize performance with regards to key components such as shape optimization, system level integration, and conjugate heat transfer.

Join PADT’s systems application engineer and heat exchanger expert Josh Stout for an in-depth look at challenges facing engineers working within this application, Ansys capabilities that can provide solutions, and examples of outputs expected after implementing simulation. 

Discussion topics will include:

  • Diffuser & Tube Thread Shape Optimization
  • Conjugate Heat Transfer
  • Cold & Hot Cycle Fatigue
  • Condensation & Evaporation
  • System-level Capability (0D, 1D, 3D Coupling)
  • And Much More

Register Here

If this is your first time registering for one of our Bright Talk webinars, simply click the link and fill out the attached form. We promise that the information you provide will only be shared with those promoting the event (PADT).

You will only have to do this once! For all future webinars, you can simply click the link, add the reminder to your calendar and you’re good to go!

3D printed jewelry box lid

New Year, New Cool Parts printed at PADT

Industrial 3D printing doesn’t have to be all about super practical jigs, fixtures and end-use parts, as impressive as those can be. Sometimes it helps to expand our vision of what’s possible either by printing cool parts we’ve found online (often at the Stratasys resource page) or by creating our own here in the 3D Printing support department at PADT. We thought it would be a good start to the new year to show them off, so here are our current favorites to inspire you, along with notes about their production.

Lens Cap Mechanical Iris

A few years ago, a clever Stratasys product-development customer designed and printed a camera-lens cover with an integrated, movable iris – a mechanical design that was only possible with FDM soluble support material. The customer even paused the print to insert a glass lens, then resumed the build (printed in black ASA) for the final layers. This is one of our favorite F370 printer files due to the “wow” response of people seeing the iris vanes open and close with a twist of the frame. (Part size: approximately 3 inches diameter, build time 2.5 hours.)

Stratasys FDM 3D printed camera lens-cover with integrated shutter-vanes. Printed in black ASA material. (Image courtesy Stratasys)
Stratasys FDM 3D printed camera lens-cover with integrated shutter-vanes. Printed in black ASA material. (Image courtesy Stratasys)

A Bolt … with an Easter Egg

It’s always fun when an interesting part displays a hidden surprise. That was the case with a little give-away model designed by PADT 3D Printing Application Engineer, Chase Wallace, to highlight the fine detail possible with prints on the Stratasys Origin One DLP resin printer. Chase designed what at first appears to be a nicely threaded polymer bolt with the PADT logo on its head and P3 (for Programmable PhotoPolymerization) on its base.

Bolt model printed on a Stratasys Origin One P3 printer in BASF ST45 resin. (Image courtesy PADT Inc.)
Bolt model printed on a Stratasys Origin One P3 printer in BASF ST45 resin. (Image courtesy PADT Inc.)

But, with a little left-handed screw action, you find the threaded section is actually a sleeve, itself threaded, internally…

The bolt is actually a two-piece assembly: there is a reverse-threaded sleeve. (Image courtesy PADT Inc.)
The bolt is actually a two-piece assembly: there is a reverse-threaded sleeve. (Image courtesy PADT Inc.)

…revealing an inner tab embossed with the Origin One label and PADT logo.

Inside the Origin One bolt sample is a tab with crisply printed logos.    (Images courtesy PADT Inc.)
Inside the Origin One bolt sample is a tab with crisply printed logos. (Images courtesy PADT Inc.)

We printed several hundred of these in BASF ST45 resin on our Origin printer. Each build produced either 32 or 24 parts, needing no support structures, in a little over two hours.

Mini-Arizona Panorama PolyJet Part

Coming up with a sample part that shows off multiple capabilities of a single printer can be a challenge, but AE Chase was also up to this task highlighting our J55 PolyJet printer, with another giveaway part.

This printer deposits millions of droplets of liquid resin (CMYK, white, clear, elastomer and more), producing parts in full color with texture and internal details. This little part is like a folding picture-frame, showing the company logo and printer model number on the front/back “covers” plus an Arizona sunset and a textured pattern on the hinged inside. (Printed open/flat, the part is about 3.7 by 0.8 by 0.5 inches; 28 parts fit on a single J55 build and print in 6.75 hours.)

Color plus clear plus texture plus an Arizona sunset - print them all on a Stratasys J55 PolyJet 3D printer, and make the part a hinged assembly, too. (Image courtesy PADT Inc.)
Color plus clear plus texture plus an Arizona sunset – print them all on a Stratasys J55 PolyJet 3D printer, and make the part a hinged assembly, too. (Image courtesy PADT Inc.)

Bento Box Personalized Gift

Lastly, we brought together the versatility of two different Stratasys technologies in a design we created to celebrate the recent retirement of a PADT co-worker. Wanting a gift that would be both fun and functional, we chose a Bento box concept with three layers of trays that nest snugly onto each other. The lid and front panels (produced on the J55 PolyJet printer) offered space for colorful artistic customization, then we printed the trays in a matching ABS on an F370 FDM system.

Custom Bento-style jewelry box, 3D printed using two different Stratasys technologies: FDM (three trays) and PolyJet (lid and front facades). (Image courtesy PADT Inc.)
Custom Bento-style jewelry box, 3D printed using two different Stratasys technologies: FDM (three trays) and PolyJet (lid and front facades). (Image courtesy PADT Inc.)

Each layer included a recessed area on the front, where we inserted J55-printed facades with text, years of service and the PADT logo, using custom colors to match the ivory filament. Since the fine 0.007-inch FDM layers made it easy to also print a visible texture, we incorporated a scrollwork-and-strawberry motif on the sides.

Side view of layered box, printed with embossed strawberry swirl pattern on a Stratasys F370 FDM printer (ABS). (Image courtesy PADT Inc.)
Side view of layered box, printed with embossed strawberry swirl pattern on a Stratasys F370 FDM printer (ABS). (Image courtesy PADT Inc.)

Inside each layer, it was easy to create removable, FDM dividers.

Removable 3D printed dividers make this jewelry box extra versatile.      (Image courtesy PADT Inc.)
Removable 3D printed dividers make this jewelry box extra versatile. (Image courtesy PADT Inc.)

And for the box lid, we found a freeware DXF scroll pattern, imported it as an editable sketch file in SolidWorks and extruded it as a cut-out overlay. We then assigned a rich aqua color to the background layer (HEX #40e0d0) and a light ivory (HEX #f7f0d2) to the overlay and frame. The final touch was a customized oval nameplate that incorporated a discrete red strawberry as the dot of the “i.” Of course, the entire lid was printed as a single piece. (Part size 7.5 by 4.5 inches; print time 6.8 hours.)

The personalized PolyJet jewelry-box lid features a recessed floral cut-out pattern in ivory, with a background layer of deep aqua, all printed as a single part. Forming the dot of the "i" with a red strawberry added a final touch of color. (Image courtesy PADT Inc.)
The personalized PolyJet jewelry-box lid features a recessed floral cut-out pattern in ivory, with a background layer of deep aqua, all printed as a single part. Forming the dot of the “i” with a red strawberry added a final touch of color. (Image courtesy PADT Inc.)

If you have a clever CAD model that just begs to be 3D printed, we’re here to help.

PADT Inc. is a globally recognized provider of Numerical Simulation, Product Development and 3D Printing/3D Scanning products and services. For more information on Stratasys printers and materials, contact us at

All Things Ansys 104: Looking Forward to 2022


Published on: January 24th, 2022
With: Eric Miller & Simulation Support Team

In this episode your host and Co-Founder of PADT, Eric Miller is joined by PADT’s Simulation Support Team for a discussion on what the new year will bring for Ansys tools and end users alike.

If you have any questions, comments, or would like to suggest a topic for the next episode, shoot us an email at we would love to hear from you!



Simulation Best Practices for Gas Turbine Design & Development – Webinar

Designing gas turbines to meet performance and safety standards remains a challenging process, and simulation is an integral part of said process. Original equipment manufacturers (OEMs) demand robust, fast and accurate solutions to reach optimized designs the first time.

Ansys offers a best-in-class multiphysics simulation solution for all gas turbine modules from inlet to exhaust. The end-to-end solution helps engine manufacturers increase safety, performance and efficiency while reducing emissions, noise, weight and maintenance cost.

Join PADT’s Senior Application Engineer and turbine expert Daniel Chaparro for an in-depth look at challenges facing engineers working with gas turbines, Ansys capabilities that can provide solutions, and examples of expected outputs after implementation. 

Discussion topics will include:

  • Aerodynamic performance
  • Combustion, acoustics and aerothermal
  • Structural durability and reliability
  • Process Compression
  • And much more

Register Here

If this is your first time registering for one of our Bright Talk webinars, simply click the link and fill out the attached form. We promise that the information you provide will only be shared with those promoting the event (PADT).

You will only have to do this once! For all future webinars, you can simply click the link, add the reminder to your calendar and you’re good to go!

Using a Table for Transient Actions in Flownex

Happy New Year! Today I want to show how we can easily use the new “Table” option to vary an input to our transient simulation. In this demo I am using Flownex version

Building the Fluid Network

If you’re most interested in how to implement the table for the transient inputs feel free to scroll past these next few sections. We’re going to go over the basic network building steps in case the information is found useful.

I chose to use a very simple network of a pipe with water flowing through it exposed to ambient air. We’ll use commercial steel for the pipe, with an inner diameter of 1 inch and a length of 100 feet. In my mind I’m pretending this is an irrigation line and as such I will add a restrictor at the end to represent something like a sprinkler head.

Heat Transfer to Ambient

The next thing we’ll want to do is model the heat transfer to ambient by way of a Composite Heat Transfer element. I have the upstream side connected to my pipe and will take advantage of that when getting areas for conduction and convection.

We can change the conduction areas drop-down to “use upstream pipe areas” and add an appropriate thickness and material type:

For upstream convection (water side), we can choose an appropriate correlation for calculating the convective heat transfer coefficient. Notice where we are obtaining inputs from the area specified in conduction and from the attached flow component. This saves us the effort of redundant calculations/inputs.

On the downstream side (air) we will set the composite heat transfer element for convection to ambient. For this set of inputs I still use the area specified in convection and then choose appropriate calculation operations for natural convection.

The key input we will be manipulating in the transient simulation is “T ambient” from the downstream composite heat transfer component. I will drag this property onto the canvas so we can easily monitor it during the run.

Setting up the Transient Scenario

What I’d like to model transiently is the effect of the changing ambient temperature on the temperature of the water in the pipe. To create a new transient scenario we go to the Configuration ribbon, click on actions setup, then in the Actions Setup Window we will right-click and “add scenario”

Since we will be manipulating the ambient temperature we will want to drag and drop this input into our newly created transient scenario as an action:

Using Table for Transient Action

We should choose “Table” under ValueType if we want to use the new Table option for varying our input transiently. I am going to use weather data for earlier this week for Phoenix, Arizona as my table of inputs. To make things easier I have converted the time to minutes after midnight.

TimeMinutes After MidnightTemp [°F]HumidityWindWind SpeedCondition
12:15 AM154283 %ESE6 mphFair
12:35 AM354186 %E5 mphFair
12:55 AM554086 %E5 mphFair
1:15 AM753889 %SE7 mphFair
1:35 AM953987 %SE9 mphFair
1:55 AM1154084 %ESE6 mphFair
2:15 AM1353985 %SE6 mphFair
2:35 AM1553887 %SSE7 mphFair
2:55 AM1753887 %SSE9 mphFair
3:15 AM1953887 %SE7 mphFair
3:35 AM2153886 %ESE7 mphFair
3:55 AM2353884 %ESE7 mphFair
4:15 AM2553886 %NE7 mphFair
4:35 AM2753885 %E8 mphFair
4:55 AM2953787 %E5 mphFair
5:50 AM3153781 %ESE8 mphFair
6:47 AM4073975 %ESE8 mphFair
7:50 AM4703781 %E6 mphFair
8:54 AM5344370 %ESE5 mphFair
9:50 AM5904854 %SE7 mphFair
10:50 AM6505250 %SW3 mphFair
11:50 AM7105544 %CALM0 mphFair
12:50 PM7705741 %WNW3 mphFair
1:50 PM8306136 %WNW5 mphFair
2:50 PM8906136 %CALM0 mphFair
3:50 PM9506332 %SW3 mphFair
4:50 PM10106332 %CALM0 mphFair
5:47 PM10675939 %S5 mphFair
6:47 PM11275544 %VAR5 mphFair
7:47 PM11875258 %SSE3 mphFair
8:47 PM12474871 %E5 mphFair
9:47 PM13074676 %ESE8 mphFair
10:50 PM13704581 %ESE6 mphFair
11:47 PM14274581 %ESE7 mphFair

The next step is to simply copy and paste or drag and drop our series of values into our new table.

Let’s run a transient and see how it behaves! Note that I’ve added an increment plot showing the temperature profile as a function of linear length of the pipe. I also modified my inlet boundary condition so that we’d have a more observable change in temp over the length of the pipe.

Although the outlet temperature stays relatively constant, if we look at the change overlaid with the changing ambient temperature we see the expected correlation. An interesting next step might be to incorporate the wind speed data and model the external convection as forced convection where we vary the wind speed according to our table.

A PADT Engineer in King Attiball’s Court – Chapter 10

There just is not enough engineer-focused fiction out there. Romance, Horror, Sci-Fi, Young Adult, Historical, Mystery, etc. They all do well, but they are rarely written for the engineers of the world.

Here at PADT, we are all about undoing such injustices. We decided to brainstorm a story about an engineer who does simulation and 3D Printing and ends up on an adventure. We hope they will find some mystery, some science fiction, and some horror. Maybe even a little romance. To develop the characters and the plot we all got on an MS Teams meeting and blocked it out. It was a lot of fun. That turned into an outline, that will turn into a chapter every month.

We hope you enjoy the result as much as we enjoyed dreaming the journey up.

It should be noted that every character in this story is completely made up. Sometimes we steal some names from real people as a shoutout to them, but that is about it. PADT does not have a basement or a fancy cluster in one. Everything is made up. Well, almost everything. We do have a stack of furniture in the back of shipping and receiving.

Chapter 10
Party and Pursuit

Takaa was prophetic. The entire town had been celebrating for three full days. And Ash had a headache that would not go away. She and her friends had been eating, drinking, and dancing well until the early hours of the morning. Although her head was still foggy about the details, she did remember a very drunk Verihbitt clinging to her in the hallway, slurring her words, and tapping Ash on the saying, “This is the last night of cela.. cela… being happy about winning. Tomorrow we start planning our counter at… atta… fight where we go to them.”

The last thing Ash wanted to do was leave the comfort of her bed. Duzi was snoring next to her. The time she had spent alone with him over the three days had been almost dreamlike. She had never seen him this relaxed and happy. At times she even forgot that she would have to leave soon. 

Outside the window, she could hear the noises of the town and, in the distance, the constant sound of the surf pounding the shore. And looking out the window, Ash could see white clouds drifting lazily by. Noone and nothing was in a hurry. But, it was time to move on. The celebration had been a nice escape. She had not charged her phone or worked on the calculator. She knew that her parents and her friends were probably worried and felt guilty that she had not worked towards getting back to them.

Rolling on her side, she pulled a protruding duck feather from the mattress they slept on and used it to gently tickle Duzi’s nose. Still asleep, he raised a hand to swat it away. Ash grabbed the hand, brought it to her lips, and gave it a gentle kiss.

Duzi smiled and stretched under the linen sheets. Then he let out a loud groan and said, “aaaaahhhh!. My head!”

Ash leaned over him and kissed his forehead. “Wake up, my darling, we have work to do today.”

She felt his hands slide to the small of her back and pull her down onto him.

He said, “Not yet, my smart one. We have other work to do first.”

The sun was well past its zenith when they walked into the courtyard to find their friends lounging around a low table, talking in quiet towns.

Alim smiled when he saw the couple approach and said, “Look who has decided to join our planning session. Our warrior and our scholar. “

Everyone turned to smile at them. Verihbitt added, “we are not going to ask where you two have been.”

Mnihh’dm rose and pulled two stools from the edge of the courtyard to the table as the others spread out to make room. A crude map was covering the table. It showed an island sheltered in a natural harbor with the name Motye written above the island. She knew it was an island just off the west coast of Sicily, one of many Phoenician trading outposts spread around the rim of the Mediterranean sea. Ash’s LARPing group often talked about organizing a trip there someday.

Alim pointed at the island and said, “We captured several sailors and some officers when they washed up on the shore. Most of them were more afraid of their King than us. Those died without telling us anything. A few cracked, and we learned that when what was left of the fleet fled and everyone received orders to regroup here, at Motye.”

Takaa added, “It seems they took over this trading post first and have since turned it into their rabbit hole. One captain, who claimed to have twenty children he wanted to see again, claimed they have set up their mirrors on the island along with enough supplies to last them a while.”

Thinking about the situation, Ash asked, “I guess we can’t try the same night-time attack?”

Verihbitt nodded. “They will be expecting that, but we can still attack at night or on a cloudy day. The problem,” she drew a big circle around the island with her finger, “is that our father-of-many also told us around half a two hundred bowmen are stationed on the island.”

Mnihh’dm pointed to the western side of the island, “If we can get our ships to beach here, we can overwhelm them. The problem is getting that close with so many archers.”

Ash thought for a while. The military success of the Phoenician empire was built on their bowman, and she assumed that this King Gula was taking advantage of this mastery. Imagining their boats rowing towards the beach, Ash could visualize the cloud of arrows descending on the unprotected oarsmen. Unless, she thought, they were protected somehow.

“Duzi, did any of the attacking ships wash up on the beaches near here?”

“Yes, a good score or so did. They are all badly burned, though.”

“What about their mirrors? Did any have mirrors?”

“Yes, be we ruined them by covering them with die. We are planning to melt them down and sell the copper to help pay for all of this.”

“Don’t do that yet. That much copper sheeting may come in handy. Let’s all take a walk to the harbor.”

Fifteen minutes later, she was telling a group of dockworkers to tie the remaining rowing skulls together, three in front and three in the back, to make a large parge.

“Druzi, do you think you could pull this behind your ship?”

“Yes, but that doesn’t hold enough men to survive an archery attack.”

“You are right, but if we put our fastest runners on board, and we protect them, do you think they could run into archers and attack them? Would that allow your ship and a few cargo vessels to land behind them?”

“Yes, but what about their mirrors? There is no way we could get them before they set us on fire.”

She looked at the makeshift barge and said, “We will land at night?”

Mnihh’dm spoke up, “But even with a full moon, there won’t be enough light for us to attack.”

Ash smiled. “We will bring our own light.”

For two weeks, Ash worked on her inventions for the attack and the calculator. She sent some short texts back to the future letting them know she was OK or asking for clarifications on the complex analog computer she would use to determine her exact time and location.   Then, after a long day, her friends would gather for some food and to share the status of everyone’s project. These were followed by late evenings with Duzi. Every morning was more bittersweet than the last because each dawn brought her closer to returning home.

The first task had been to pound out the recovered copper sheets and shape them into peaked covers for the outrigger. An arrow would go straight through them if fired head-on, but they would deflect off a peaked roof. That was the easy part. Building spotlights was going to be more difficult.

She had never thought about it before, but the only way to make light in the ancient world was by burning wood or oil. Working with Alim, Ash experimented with different combinations and found that wool soaked in olive oil, with a little sea salt, gave off the brightest flames. She then instructed the artisans to repolish some of the copper to make reflectors. They then mounted the reflectors to the back of clay bowls that held the wool torches.

When enough of these beacons were added to her barge, they could illuminate a nearby beach, even on a moonless night. It was not perfect. Ahe didn’t have the time to play with minerals in an attempt to make a flare. This would have to do.

Her last morning in Tripoli started with a gentle kiss from Duzi.  “Rise and shine my little scholar. We have to catch the tide.” They ended up arriving late.

The group was gathered for a quick breakfast in the courtyard. All of Ash’s gear was now on the ship, safely stowed away.

She walked over to where Verhibitt was eating and sat beside her. Her whole mindset had changed when it became obvious that they would be leaving in less than an hour.

Ash said, “I am scared.”

Verhibitt took a bite of bread and then said, “You have been through this before, worse maybe. We will be safe on Duzi’s ship.”

“I know. But before, everything happened so fast. I have had two weeks to think of everything that can go wrong.”

Yes,” said Verhibitt. “Sometimes, extra time can make things worse. Try not to spend too much of your day, or your nights, in thoughts about what might happen. That is for Baal to decide. Not you.”

Ash was a little surprised. She had never heard Verhibitt envoke the Phoenician deity before.

“You look shocked. I mentioned Baal.” Verhibitt took a deep breath. “Well, maybe this time I am also more than a little scared. Maybe this time I am looking for a little help.”

At high tide, they moved down to the harbor and boarded their mini-fleet. Five cargo vessels crammed full of as many soldiers as they could gather rowed out of the harbor behind them, following the towed barge. The wind was behind them, so they dropped sails, and the oarsmen laid around the deck, playing dice and sharpening their weapons.

Ash used the time to work on the calculator. All of the brass components were cut and shaped. All that remained was to put it together. And that was turning out to be very hard.

Back in the twenty-first century, making precisions components was easy. She could have used rigid metals and precision CNC machines. Now, working with soft brass and everything hand-made, she had to assemble each part then file it by hand to fit. Ash remembered watching documentaries about Swiss watchmakers that built timepieces the same way. She never thought she would be arched over a bench sailing across the Mediterranean,  doing the same thing. And without a magnifying glass.

Verhibitt came to sit with her on their second day at sea.

“I don’t know how you can sit here for so long and file away at your little project. I am going crazy just watching you.”

“I’m not sure how I am doing it. I guess I do not have a choice if I want to go home.”



“Do you really want to go back to your land?”

Ash thought about the question. About her friendship with Verhibitt and her romance with Duzi. They were wonderful people, and she had had so many amazing adventures. 

“I think about it all the time. Every morning and every night. But as much as I have felt so welcome here, and have built friendships…” Ash paused, looking for the right word.

“More than a friendship?” Verhibitt offered.

“Yes, and that. I have never felt like this about anyone before. I have had what we call boyfriends. But never like this. The problem is, with all of that, I just do not belong here. Hear and now is not my place in the world.”

Verhibitt sat and watched Ash work for a long time before she said, “I see that.”

And that was the last time they talked about it.

The next day they arrived off the south shore of Sicily. Stowing the sails, they rowed way from shore and waited for the sun to go down. Everyone was preparing for the battle, including Ash, who was storing her phone and the calculator safely inside storage crates. She then covered them with wet hides to protect them from fire. Behind them, the soldiers were preparing the barge, soaking the wool in the baskets with olive oil.

Then they waited for the sun to go down and for the sea and the beach to become dark.

When Druzi decided it was safe enough, everyone moved into position, and they used to stars to row west, then north to the small lagoon The moon was just a sliver, so that did not help much. Finding the opening to the lagoon and then the island were the biggest risks of their plan. 

Then they saw light on the horizon. As the small collection of boats moved closer, they could make out a large bonfire on a beach. Silently, they rowed towards it, and as they got closer, it became clear that this was the island they had been looking for.

Duzi came back to confer with the group at the back of the ship.

“It looks like our King is so arrogant, he has set up his own bonfire. And even better, it is on the other side of the island. If we keep our distance and circle around, we can use our own lights to attack the beach we want to land on, and they will be blinded by their own flames.”

“Are you sure?” asked Mnihh’dm.  “This seems a little too easy.” 

Verhibitt laughed. “I think if the gods smote the island with lightning in front of us, you would claim that it was a trick.”

Mnihh’dm grumbled, “it just doesn’t feel right.”

They moved as planned, keeping as far away from the island as possible till the North star showed that they were east. They stopped and let the barge loose. Soon, the soldiers on board began to row to the front of the small armada. When they were between the ships and the shore,  Duzi uncovered a small lamp to signal the beginning of the attack.

Ash could see white foam catch the dim moonlight as the soldiers in the barge began to paddle as fast as they could. Then, a few hundred yards from the beach, they lit the torches. She could now see the beach outlined in the growing flames, reflected by her makeshift searchlights. The archers were nowhere to be seen. 

She turned to Verhibitt and said, “This may be easier than we thought.”

And then she heard the shouts. 

Soldiers on the deck of one of the cargo ships were screaming. She could just make out that they were pointing to the left of the barge. A huge trireme came out of the darkness into the light created by the barge. In seconds, it smashed right into its side.

The sound of splitting timber and screaming men ripped through the air. Before they could really see the damage, the torchers went out as the barge broke apart and sank. They were in near darkness again and had lost their lightning attack force.

Ash watched the huge trireme slowly turn towards them and then gain speed as it moved to ram one of the cargo ships. Duzi was barking orders, and the soldiers on each ship began to row as well. Ash ralized they were not moving towards the attacking ship. They were going to storm the beach.

Druzi screamed, “Faster, you worthless dogs! They are too big to get close to the shore! We need to beat them in!”

Holding her breath, Ash felt the ship leap forward and head straight for the shore, the cargo ships close behind. 


Ash heard the sound of timber rending again and turned, expecting to see one of the cargo ships breaking apart on the bow of the trireme. Instead, she saw the huge three-deck ship light up as fire broke out on the deck as it broke in half. 

Verihibitt shouted over the noise, “It must have hit a rock! Maybe I need to talk to Baal more often!”

Then Ash was lurching forward, trying to grab onto something as the ship came to an abrupt stop on the beach. When she stood up again, she saw that Duzi’s men were jumping over the railing and joining up in formations on the beach. Their cargo ships and the soldiers on board soon joined them.

Everyone relaxed a little, setting up defensive formations preparing to march to the fort on the other side of the island.

Then the arrows came. 

In the dark, it was hard to tell where the projectiles were coming from. Duzi sent ot squads in every direction, searching. Soon, a group to the left was soon yelling for everyone to join them. Ash watched in shock as half of the soldiers ran into the darkness while the other half took up a defensive position on the beach. They dragged those injured by the archer attack back to the ships.

The sound of fighting reached them from a distance, and Ash began to feel panic grow in her. Every battle she had been in so far was over in minutes. It had been over thirty minutes since they had slammed into the beach, and the small group was still out there fighting. 

She felt tears coming to her eyes. The fight was taking too long, and Ash began to give up hope. Then she saw a tall figure slowly walking towards them in the light from the still burning trireme. When they realized it was Takaa, she and Verihibitt leaped to the sand and ran towards him. As they got closer, she realized he was dragging someone by the neck.

He stopped short and kneeled in the sand, still holding on to the squirming figure.

Panting for breath, he said, “The battle is done. We lost about half of our men, but we sent their men scrambling back to their fort. They are locked inside now.”

Verihibitt kneeled next to him, took his face in her hands, and kissed him deeply, and then said, “I am so glad to see you.”

The squirming man that Takaa was still holding in his large hands spat at Verhibit and yelled, “You whore!”

Someone brought a torch, and they could see that Takaa’s captive was Verhibitt’s former betrothed, Ahinadab.

– To Be Continued –

Please subscribe to our newsletter, so you will know when the next installment, “Siege and Showdown,” wherein, our intrepid crew corner their prey, and work to draw the evil king from his fortifications.

Phoenician Temple, Motya, Sicily. - Stock Image - C047/4704 - Science Photo  Library
The remains of a Phonecian Temple in Motya, Sicily

All Things Ansys 103: 2021 Wrap-up & Predictions for Ansys in the New Year


Published on: December 15th, 2021
With: Eric Miller & Simulation Support Team

In this episode your host and Co-Founder of PADT, Eric Miller is joined by PADT’s Simulation Support Team for a round-table discussion of their favorite Ansys features released in 2021, along with predictions on what has yet to come.

If you have any questions, comments, or would like to suggest a topic for the next episode, shoot us an email at we would love to hear from you!



Surprise – 2021 Turned out to Be a Lot Like 2020

The problem with making predictions and publishing them is that you can’t hide from how incredibly wrong you were. This time last year, I wrote, “Good Times and Bad Times – 2020 has been a year to remember.” And at the end, I made predictions for 2021. It actually says, “Like most people, we will be working under #covidrules through the first quarter and maybe even a bit into April or May.”

Well, we got that wrong.

Although vaccination and safety measures have allowed many of our employees to return to the office, and we have been traveling much more through 2021 than the previous year, we are still working under #covidrules. The rules are different, but we never got to the “new normal” that we all anticipated. That is the bad news. The good news is that 2021 turned out to be another good year for PADT.

The good news is that everyone is healthy, and although a few employees and their family members got sick, everyone has come through it OK. And being the amazing people everyone at PADT is, they adapted to every curveball that the year sent their way. And as the months quickly moved by, we continued to add to our sales and support capability while still excelling on the technical side.

The First Half of 2021 was all About Growing Sales and Support Capability

We started the new year off with the addition of Jim Sanford as our new Vice President of Sales & Support. After years of growth in both personnel and customers, we needed a strategic leader who could build on the success PADT has built over the years to become an Ansys Elite and Stratasys Diamond Channel Partner. His leadership experience at Siemens, MSC, and Dassault has proved invaluable and served the team and our customers well as we increased our sales and support capability across the first half of the year.

Stratasys recognized our multi-year success in March of 2021 by elevating PADT’s status from Platinum to Diamond Channel Partner. PADT has been using, supporting, and selling Stratasys 3D Printers in the four-corner region since the late 1990s. In March, when Stratasys announced the status change, we had sold 883 printers to 506 customers in the region. Our sales and support team in Arizona, Colorado, New Mexico, Texas, and Utah worked hard through 2021 to add to those numbers.

Other digital manufacturing OEMs noticed our success, and PADT became a reseller for EOS Metal 3D Printers in March, then optical and laser scanning systems from #HandsOnMetrology in April. EOS is the leading provider of metal, Laser Powder Bed Fusion systems in the world. #HandsOnMetrology is the result of ZEISS and GOM merging their 3D scanning solutions to create the leading provider in that area as well.

All of that growth required a larger, restructured team. So in June and July, we reorganized the Simulation and 3D Printing sales and support team to better respond to customers. This included promoting Ted Harris, Alan McNeil, and Kathryn Pesta to Director level positions overseeing simulation support, enterprise solutions, and sales operations, respectively. To assist Ted, long-time Ansys technical expert Doug Oatis took over as the leader of the application engineering team. We also added three new engineers to support simulation and 3D Printing customers.

Looking back at the end of the year, all of these improvements turned out well. The growth of simulation, 3D Printing, and scanning use at existing and new customers is just one metric. We have also successfully added new products in both the Ansys and Stratasys family as well as the two new product lines mentioned above. All while keeping our customers productive as they grow and adapt to the changes 2020 and 2021 have delivered.

The Second Half was About Technological Innovation

PADT’s growth and success in Sales and Support is partially a result of the company’s long tradition of technical excellence. When engineering organizations are stressed, they count on partners who step up and step in to help. That is what PADT’s engineers did across 2021. This was highlighted in the second half of the year in several ways.

The first was the release of PADT’s tool that converts Ansys Mechanical results into a 3MF file. PADT’s unique position as expert in both 3D Printing and Simulation enabled our engineers to create this powerful tool that can be downloaded from the Ansys Store. “AM Result Printer” is also a great example of PADT’s ability to use the open API in Ansys products to create customer utilities and applications.

Speaking of our unique Simulation and 3D Printing expertise, NASA awarded PADT a Phase III STTR Research Grant to continue our work with Universities to utilize bio-inspired geometries in space structures. In this phase of the research, PADT will work with Penn State University to integrate the optimization tools we developed in-house with their CFD optimization tools to do multiphysics topological optimization.

The final recognition of technical achievement came in November when PADT employees were listed as Co-Inventor on two patents. A little research showed that current or former PADT employees were listed on 16 total patents in 2020 and 2021. That is an impressive number and a strong endorsement of the innovative capabilities of PADT’s technical team.

We Did Have a Chance to Get Together

Although many events were hybrid or virtual-only, we were able to safely gather for a few important forums. We exhibit and present at the Design & Manufacturing | MD&M Show in Anaheim, the Space Symposium in Colorado Springs, the New Mexico Tech Council’s experienceITnm, and multiple Arizona Technology Council events, including this year’s Governor’s Celebration of Innovation. I was able to attend the signing of the Arizona Angel Tax Credit Extension, Venture Madness, and UnMet in person. But best of all, we were able to hold our annual Nerdtoberfest open house at PADT in October. It was mostly outside, but still a great gathering.

Many salespeople and support engineers were able to visit customers, and a few customers visited our offices every week. We also held a few teambuilding events both in person and virtually and many of our employees were finally able to take a vacation and see family and friends around the world. Not as much travel or interactions as we had hoped, but it was good to bring a pocket full of masks and get out and about.

PADT is Ready for 2022

We learned our lesson last year. There will be no predictions for 2022.

What we do know is it will surprise us, our customers will count on us to be there, and we know for certain that PADT’ outstanding employees will rise to whatever challenges the year brings.

Our goals for 2022 are:

  • Venture out and about as much as possible
  • Continue to support local, regional, and national events wether virtual, hybrid, or in person.
  • Build on the growth we saw in 2021 in our sales and marketing team.
  • Continue to devlop our technical leadership
  • Make the best of whatever the year throws our way

As Always, Thank You!

Like last year, PADT is extremely fortunate to have had a good year both personally and professionally. It has been much worse for many people and we are thankful for our partners, our customers, and our employees.