Commit graph

24 commits

Author SHA1 Message Date
9cdc2491b1 Small issue reading edges
Sometimes I do things right, then I change them thinking my old self was
an idiot and then they break.

The positive point: the solutions end up being better.
2026-02-27 20:55:07 +01:00
ce6b6a41a6 New physical surfaces implemented 2026-02-20 09:50:42 +01:00
a0d45503f7 Working on init for new physical surfaces 2026-02-19 20:42:28 +01:00
d211ed9a71 Almost done with EM, not to modify the EM module itself 2026-02-18 15:14:59 +01:00
4c72e68246 Boundaries for EM almost done 2026-02-18 13:31:38 +01:00
6f8656bc21 Init for boundaries particles 2026-02-16 20:05:23 +01:00
58e2fa7566 Working towards compilation with submodules 2026-02-09 13:52:52 +01:00
1b1a574edc Read initial
Now we can read an initial condition as we do with other formats.

Only documentation left.
2026-01-23 15:04:39 +01:00
ac27725940 Big one...
I should've commited before, but I wanted to make things compile.

The big change is that I've added a global time step so the parameter
does not need to be passed in each function. This is useful as we are
moving towards using time profiles for boundary conditions and injection
of particles (not in this branch, but in the future and the procedure
will be quite similar)
2024-07-12 23:08:19 +02:00
152ae6b097 No longer needed
The correction in the node volume is no longer needed as now things are
being calculated right with the last change.

Still, at some point I should review the calculation of the node volume
in 2DCyl.
2024-07-11 18:19:26 +02:00
bc8f205287 Clean-up!
Trying to reduce warnings and unused variables in the code. This should
not be in this branch.
2024-07-11 15:55:02 +02:00
d608639e77 Forgot to save
Sorry.
2024-07-09 22:05:16 +02:00
667a2ecd93 So, no idea...
Basically things do not work. I've added a correction to the node volume
in the axis which gives okays results but still this is not perfect. I
need to find a better way to do things.

Also, I've noticed that the density changes with the size of the cells,
which should not happen! I'vw to check this issue.
2024-07-09 21:57:32 +02:00
b36f9c2615 Shifting towards constant number of particles per edge
So now each edge has the same number of particles and the weight of each
particle is calculated based on the surface of each edge compared to the
total one.

Only in 2DCyl, still to extend to other geometries.

Not perfect constant density, but the issue might be the node volume.
2024-07-09 17:49:42 +02:00
626e970d82 Some progress
Fixed an issue with random integer numbers.
Cylindrical coordinates are not perfect yet:
  - Box (cylinder) with initial constant density loses particles at r =
    0
  - Injection density still low in r = 0
2024-07-06 19:14:44 +02:00
e9ac9bdd80 Finishing implementation of vtu mesh format
I have tested all geometries and cases and all seem to work perfectly
with .vtu meshes.

Input and output works great, starting from a previous case also works.
Everything I was able to test is okay.

Still, what I want to do is to change a few things in the output (e.g.,
    change OUTPUT prefix to Step) and try to improve reading gmsh meshes
to make them more compact as vtu is now.
2023-02-07 15:19:13 +01:00
ba2b5bc6f3 Fixed issue with initial velocity
The problem was that the number of values for velocity was numNodes and
not 3*numNodes.
2023-02-07 09:43:28 +01:00
515e5c7744 Fix an issue and starting to read information from .vtu initial files
For some reason the connectivity for collision meshes was not being
properly assigned.

Also, the first subroutine to read information from .vtu files as
initial states has been added.
It is currently giving wrong results.
2023-02-06 19:54:54 +01:00
a22099ee87 Improvement to vtu read subroutine
Some improvements to reduce code repetition when reading vtu mesh.
2023-02-06 19:18:04 +01:00
e3eeb97f48 First working version!
First complete implementation of .vtu format.
Still a lot of things to improve but right now fpakc can read a vtu mesh
and write the output in vtu.

Still to test:
  Multiple geometries.
  Double mesh.
2023-02-05 21:33:03 +01:00
43a7421795 Creating of nodes and edges in .vtu format
Moving forward making vtu an independent format.

Now fpakc can generate nodes and edges from vtu input.
Next step is cells.

Some minor corrections in gmsh2 format to unify statements.
The reading of meshes needs a good overhaul.

Testing all geometries with vtu is gonna be fun...
2023-02-05 19:35:49 +01:00
7b470b7f58 Subroutines to read .vtu information
All subroutines to read .vtu information is ready.

Now it is time to create the input and generate a mesh for fpakc.
2023-02-05 18:32:38 +01:00
63fd8fdb91 New functions to read VTU
Added a few functions to read .vtu meshes.

Output in .vtu changed to output data in 6 columns (seems to be the
    standard.)
2023-02-05 16:23:37 +01:00
f5be04587a First step towards reading .vtu mesh
Just setting up the required functions.
2023-02-04 15:41:13 +01:00