Dear Miguel,
The over-refinement was due to an overly strong hypothesis on the 1D mesh that
was made when refactoring the code in Gmsh 4.5.4. The next development snapshot
will fix this little regression.
Thanks for the report,
Christophe
> On 5 May 2020, at 15:36,
Hi all
Say I have a set of $NodeData$s with a temperature distribution from a
transient heat conduction problem but due to adaptivity the times are
not equally spaced. Each set has the real tag as a the real time and
the first integer tag as the time index.
Any (scalable) idea of how can I get
> On 4 May 2020, at 23:04, Rosicley Júnio Rodrigues Rosa
> wrote:
>
> Hello,
>
> I'm a Master student and I use Gmsh to solve fracture mechanic problems. From
> the interactive mode, I have used the plugin crack to generate a crack in a
> surface, but I need to use this plugin from the
> On 5 May 2020, at 06:15, Tian Xia wrote:
>
> Hi,
>
> First of all, I'd like to thank you for the great software. It saved me a lot
> of time.
>
> I am trying to define a mesh size field based on the distance to the volume.
> I knew that there is a command "PointsOf(volume #)" for geo
> On 5 May 2020, at 12:34, miguel.ar...@artorg.unibe.ch wrote:
>
> Dear all,
>
> I was using a code I developed in version 4.4 for meshing spheres with
> tetrahedron. I could modify the characteristic length (max. and min.) and it
> worked perfectly.
>
> Moreover, I’ve been using this
Dear all,
I was using a code I developed in version 4.4 for meshing spheres with
tetrahedron. I could modify the characteristic length (max. and min.) and it
worked perfectly.
Moreover, I’ve been using this code in different incremental updates and it
worked perfectly until version 4.5.3.
