Dear Jeremy,David

Thank you for your attention and help!

Best

Song

From: Jeremy Cohen <jeremy.cohen@imperial.ac.uk>
Sent: Tuesday, May 28, 2019 6:19:40 PM
To: Moxey, David
Cc: Song Xiang; nektar-users
Subject: Re: [Nektar-users] History point cannot be found in the mesh on the latest version
 
Many thanks for highlighting this Dave, I've just built a version based on MR 1019 and can confirm that this resolves the issue.

Cheers,
Jeremy

On 28 May 2019, at 10:04, Moxey, David <D.Moxey@exeter.ac.uk> wrote:

> Hi Jeremy, Song,
>
> You might want to try out MR 1019:
>
> https://gitlab.nektar.info/nektar/nektar/merge_requests/1019
>
> My student and I found a bug in the GetExpIndex function last week that
> might also impact the history point lookups.
>
> Cheers,
>
> Dave
>
> On 2019-05-28 09:51, Jeremy Cohen wrote:
>> Dear Song,
>>
>> Just to confirm, I've been able to recreate the error you're
>> experiencing with a recent master build and have verified that running
>> the same test case with 4.4.1 works ok. We'll investigate what is
>> causing the issue and get back to you.
>>
>> Cheers,
>> Jeremy
>>
>> On 27 May 2019, at 20:59, Sherwin, Spencer J
>> <s.sherwin@imperial.ac.uk> wrote:
>>
>>> Dear Song,
>>>
>>> What machine are you running the code on? As you can see form
>>>
>>> https://buildbot.nektar.info/#/grid
>>>
>>> The virtual machines we are currently testing the code on seem to be
>>> passing the test we have set up so I would have hoped it is running
>>> OK for you too. If you run Nektar4.5.0 on another machine do you
>>> still see the same issue?
>>>
>>> Cheers,
>>> Spencer.
>>>
>>>> On 27 May 2019, at 08:53, Song Xiang <sxnwpu@outlook.com> wrote:
>>>>
>>>> _Dear all,_
>>>> _ On the latest nektar version, 4.5.0, __there is a problem with
>>>> the given case
>>>> (AcousticSolver/Tests/APE_2DPulseAdv_WeakDG_MODIFIED.xml). When
>>>> the program runs,it will report an error "History point cannot
>>>> be found in the mesh". __However,_
>>>> when the same xml file is used on a previous nektar version,
>>>> 4.4.1, it is properly done.
>>>>
>>>> The history point is not a node of mesh but in the domain. When i
>>>> use a node of mesh as history point, the program performs well on
>>>> the latest version. Can not use the points which are not nodes of
>>>> mesh as history points now?
>>>>
>>>> Thank you.
>>>>
>>>> Cheers,
>>>> _ Song_
>>>> _______________________________________________
>>>> Nektar-users mailing list
>>>> Nektar-users@imperial.ac.uk
>>>> https://mailman.ic.ac.uk/mailman/listinfo/nektar-users
>>>
>>> Spencer Sherwin FREng, FRAeS
>>> Head, Aerodynamics,
>>> Director of Research Computing Service,
>>> Professor of Computational Fluid Mechanics,
>>> Department of Aeronautics,
>>> s.sherwin@imperial.ac.uk                                   South
>>> Kensington Campus,
>>> Phone: +44 (0)20 7594 5052                              Imperial
>>> College London,
>>> Fax:   +44 (0)20 7594 1974                               London, SW7
>>> 2AZ,  UK
>>> http://www.imperial.ac.uk/people/s.sherwin/
>>>
>>> _______________________________________________
>>> Nektar-users mailing list
>>> Nektar-users@imperial.ac.uk
>>> https://mailman.ic.ac.uk/mailman/listinfo/nektar-users
>> _______________________________________________
>> Nektar-users mailing list
>> Nektar-users@imperial.ac.uk
>> https://mailman.ic.ac.uk/mailman/listinfo/nektar-users
>
> --
> Dr David Moxey, PhD MMath MIMA FHEA
> Senior Lecturer in Engineering
> d.moxey@exeter.ac.uk | tel: 01392 424764 | web: davidmoxey.uk
>
> Room K1, Innovation Centre,
> University of Exeter,
> Exeter, EX4 4RN, UK.