# Implementing \`.series\` support for ExodusII

**URL:** https://discourse.paraview.org/t/implementing-series-support-for-exodusii/17425
**Category:** Development
**Tags:** exodus, proposal
**Created:** [February 3, 2026, 8:04am UTC](https://discourse.paraview.org/t/implementing-series-support-for-exodusii/17425 "2026-02-03T08:04:34Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![drwells](https://discourse.paraview.org/user_avatar/discourse.paraview.org/drwells/32/17453_2.png) [@drwells](https://discourse.paraview.org/u/drwells)
#### Post date: [February 3, 2026, 8:04am UTC](https://discourse.paraview.org/t/implementing-series-support-for-exodusii/17425/1 "2026-02-03T08:04:35Z")

</div>

Hello! While I could use `.ex-timeseries`, I’d prefer to use the newer `.series` syntax. I tried adding this myself by following the approach in [https://gitlab.kitware.com/paraview/paraview/-/merge\_requests/2532](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/2532) (i.e., by adding `.ex2.series` to `readers_ioioss.xml`) but that wasn’t enough to make it work.

One issue is that an ExodusII file can (mine don’t, it isn’t a usecase I need) contain multiple timesteps, and they store time values: is there a standard way of dealing with that for other file formats, e.g., if time values don’t match?

I’m willing to add this functionality myself but I’ll need some hints to get started. It would be great to get this working for all the file formats supported by the IOSS reader.