Compilation nigthmare

[jmlopez...@gmail.com]

Hi all,

I am developing a code to try to prevent the contact line from moving (but this time in 3D). I started by doing some routines it in plain C, but when I want to port it to Basilisk to use its structures and utilities (coord, foreach_dimension, etc.) I find that compilation times skyrocket and in some cases it never finishes compiling, staying seemingly frozen. With all the errors and trial runs I go through, development is turning into a heavy nightmare.

Is there any way to speed up compilations? Shall I should clean something?

Cheers

Pepe

[Kevin McTaggart]

This past week I went through an exercise with my code to determine why the interpreter was giving a warning that maximum number of iterations had been reached.  I tried incrementally adding code and compiling, but there was no obvious reason when I obtained the warning again.  I had no warning after I used flag -disable-dimensions.  I now plan to add dimensions to my code.

--
You received this message because you are subscribed to the Google Groups "basilisk-fr" group.
To unsubscribe from this group and stop receiving emails from it, send an email to basilisk-fr...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/basilisk-fr/811e6b70-aa3f-4d95-8a25-cba6fd3245cdn%40googlegroups.com.

[Stephane Popinet]

Hi Pepe,

As suggested by Kevin, try -disable-dimensions. But I am curious about
why your code is slow to compile. Can you share it?

cheers

Stephane

[jmlopez...@gmail.com]

Hi Stephane (and Kevin),

You were right! It turns out the bottleneck is indeed the dimensional analysis; disabling it solves the excessive compilation time.

I’ve attached the (seemingly problematic) code for your review.

Cheers

Pepe