To whom it may concern,
I want to refine the left bottom corner of an homogenous mesh of a square,
exponential with the translation function "e^-lambda*x". The solution should be
a stiffness matrix.
I don´t have an approach how to solve this problem. Can you give tell me the
proceeding, pls.
Hi Chrstophe
I tried setting it to "MM" and the result was the same. I will take a look
again and send a mwe illustrating the issue.
Regards
jeremy
On Mon, Dec 4, 2017, 08:45 Christophe Geuzaine wrote:
>
>
> > On 4 Dec 2017, at 10:59, Jeremy Theler wrote:
> >
> > Is the new property Geometry.
> On 3 Dec 2017, at 11:40, andrew wrote:
>
> Hi,
>
> Is there a way to access the properties of an entity like
> area/volume/length?. For example in the Boolean.geo demo is there a command
> like
>
> Volume[8].Area or Volume[8].volume?
>
No, this is not trivial. The best way is to mesh th
> On 4 Dec 2017, at 09:40, Marek Wojciechowski wrote:
>
> Dnia niedziela, 3 grudnia 2017 09:19:27 CET Christophe Geuzaine pisze:
>> To achieve these goals the API
>>
>> - is purely functional
>> - only uses basic types from the target language (C++, C or Python)
>> - is automatically generated
> On 4 Dec 2017, at 10:59, Jeremy Theler wrote:
>
> Is the new property Geometry.OCCTargetUnit working as expected?
>
Yes.
> How can I revert back to the original behavior, i.e. do not assume anything
> about units in an imported OCC model and leave them as "non-dimensional"?
Actually, whe
Is the new property Geometry.OCCTargetUnit working as expected?
How can I revert back to the original behavior, i.e. do not assume anything
about units in an imported OCC
model and leave them as "non-dimensional"?
Thanks
--
Jeremy Theler
www.seamplex.com
_
Dnia niedziela, 3 grudnia 2017 09:19:27 CET Christophe Geuzaine pisze:
> To achieve these goals the API
>
> - is purely functional
> - only uses basic types from the target language (C++, C or Python)
> - is automatically generated from a master API description file
> - is fully documented
Great
