Dear Bruno and Jean-Paul, 

The new syntax worked great, and thank you for the extra resources Bruno.  

Best, Victoria 

On Tuesday, June 9, 2020 at 11:05:50 PM UTC-4, Bruno Blais wrote:
>
> Dear Victoria,
>
> In additional to what Jean-Paul suggested, you can look at the preliminary 
> version of step-68 which does exactly what you would like to achieve with 
> particles.
> The code is available on the following pull request. Rene and I have put 
> some work into it and it works quite well in its current state:
> https://github.com/dealii/dealii/pull/10308
>
> Best
> Bruno
>
>
> On Tuesday, 9 June 2020 16:06:15 UTC-4, Jean-Paul Pelteret wrote:
>>
>> Dear Victoria,
>>
>> You’re on the right track, but it looks like you got the syntax a bit 
>> wrong. To create a particle you need to write something like
>>
>> Particles::Particle<dim> particle;
>>
>> You’ll note that the specific constructor that is called is inferred from 
>> the arguments given to the instance of the class that’s being created (in 
>> this case, no arguments —> default constructor).
>>
>> There is a new tutorial, namely step-70 
>> <https://dealii.org/current/doxygen/deal.II/step_70.html>, that uses 
>> particles. I don’t know whether or not it’s pitched at the right level for 
>> you to get to grips with some of the fundamentals (at first glance, it 
>> seems to involve a number of more advanced techniques). If it’s not quite 
>> tractable for you, then you could also take a look at some of the particle 
>> tests <https://github.com/dealii/dealii/tree/master/tests/particles> in 
>> the test suite, such as this one 
>> <https://github.com/dealii/dealii/blob/master/tests/particles/particle_01.cc>,
>>  
>> that might provide snippets of information that you need as you build up 
>> your understanding of this particular feature of the library.
>>
>> I hope that helps you a bit.
>> Best,
>> Jean-Paul
>>
>> On 09 Jun 2020, at 17:14, Victoria W. <wied...@gmail.com> wrote:
>>
>> Hello, 
>>
>> I'm a new deal.ii and C++ user, so this question might be a bit basic, 
>> but I was wondering how my implementation of the built-in deal.ii particle 
>> class should look.  Ultimately I'm looking to track a particle in laminar 
>> flow.  So far I've tried creating a simple particle at the origin after 
>> generating my geometry with the GridGenerator class.  Calling the particle 
>> class in my code looks like this: 
>>
>> Particles::Particle<dim, dim>::Particle() 
>>
>> as per the documentation on dealii.org.  However I get the error 
>> message: error: dependent-name ‘dealii::Particles::Particle<dim, 
>> dim>::Particle’ is parsed as a non-type, but instantiation yields a type.  
>> How should I be implementing this class to construct a particle, what type 
>> declaration should new particles be declared as, and are there other 
>> documentation or resources I should be looking at?  
>>
>> Thanks
>>
>> -- 
>> The deal.II project is located at http://www.dealii.org/
>> For mailing list/forum options, see 
>> https://groups.google.com/d/forum/dealii?hl=en
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "deal.II User Group" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to dea...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/dealii/43d0b22c-d736-464d-9d83-da4d819eca90o%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/dealii/43d0b22c-d736-464d-9d83-da4d819eca90o%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>>
>>

-- 
The deal.II project is located at http://www.dealii.org/
For mailing list/forum options, see 
https://groups.google.com/d/forum/dealii?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"deal.II User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dealii+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dealii/7b15eb6e-fc09-43f2-997d-e233e09829b1o%40googlegroups.com.

Reply via email to