The timestep I’m using for the simulation is 5 miliseconds, but it does not allow me to write all fields for every timestep, would be extremely large. What I’m refering to as frames is the timesteps in which the fields were written by the software, which is related to the animations I can create.
For instance, for a 5 seconds simulation it provided me only 12 frames, which means I have data for the entire field at a timestep of about 0.25 s, which is really bad to me because is half the cycle I want to capture. For a simulation of 1 s it recorded 17 frames, but this allowed me to have the fields for timesteps of about 0.05 s, way better!
I downloaded the field and checked out Paraview , I didn’t know it so thanks for the tip! I managed to create a few interesting fielters and it does allow me to create some ‘wave gauge’ by creating lines and checking the alpha along it. However I am still limited to the timesteps that I can get the fields written, the frames I mentioned. I will run the cases with less simulation time so that I can have the data at a reasonable ‘sampling rate’, and alternatively try something with the Result Control since this approach would allow me to run longer simulations and have the time at small timesteps.
Thanks a lot for the suggestions and, if I find some alternative way I will update it here!