[dealii-developers] Updated Github access rights and groups

2016-08-09 Thread Matthias Maier
Hi all,

I have updated deal.II's organizational structure on github. The most
important changes are:

 - I removed the legacy "Owners" group. Ownership is handled via the
   "owner" attribute now.

 - I have removed the collaborators group - only deal.II developers are
   now "member" of the project. This allowed me to grant all members the
   right to create repositories.

   I have transformed the collaborators group to per repository
   collaborators with suitable "Read" or "Write".

If you are affected from some of these changes, you will get a bunch of
e-mails from github.

Please check that you still have equivalent access rights. If not,
please write me an e-mail so that I can fix it.

Best,
Matthias

-- 
You received this message because you are subscribed to the Google Groups 
"deal.II developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dealii-developers+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [dealii-developers] Invalid Copy Constructor vs (Deleted Copy Constructor and Shared Pointer)

2016-08-09 Thread Jayesh Badwaik
Thank You for your reply. 

-- 
Cheers
Jayesh Badwaik

-- 
You received this message because you are subscribed to the Google Groups 
"deal.II developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dealii-developers+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: This is a digitally signed message part.


Re: [dealii-developers] step 47

2016-08-09 Thread Daniel Arndt
You might want to have a look at
http://journals.ub.uni-heidelberg.de/index.php/ans/article/view/22317/23996
This seems to be quite similar.

Best,
Daniel

Am Dienstag, 9. August 2016 19:28:51 UTC+2 schrieb bangerth:
>
> On 08/08/2016 11:55 PM, sella...@gmail.com  wrote: 
> > I am a new user of dealii and I came across the step-47 program which 
> implements level set method. But I could not find its complete 
> documentation anywhere. 
> > 
> > It would be very helpful if you could share the document explaining the 
> math behind this step. 
>
> There is none :-( The program was started in 2012, but we never finished 
> it, and nothing was ever written up. 
>
> I had always hoped that we would eventually finish it, but I don't see 
> that happening. It may be best to just delete it. 
>
> Best 
>   Wolfgang 
>

-- 
You received this message because you are subscribed to the Google Groups 
"deal.II developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dealii-developers+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [dealii-developers] step 47

2016-08-09 Thread Wolfgang Bangerth

On 08/08/2016 11:55 PM, sellam1...@gmail.com wrote:

I am a new user of dealii and I came across the step-47 program which 
implements level set method. But I could not find its complete documentation 
anywhere.

It would be very helpful if you could share the document explaining the math 
behind this step.


There is none :-( The program was started in 2012, but we never finished 
it, and nothing was ever written up.


I had always hoped that we would eventually finish it, but I don't see 
that happening. It may be best to just delete it.


Best
 Wolfgang

--
You received this message because you are subscribed to the Google Groups "deal.II 
developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dealii-developers+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [dealii-developers] Invalid Copy Constructor vs (Deleted Copy Constructor and Shared Pointer)

2016-08-09 Thread Wolfgang Bangerth


Jayesh,


I want to decide what to do with the copy constructor of the grid.
1. With the c++11, we can use the delete keyword for the copy
constructor [1]. The advantage is the copy constructor is "cleanly"
deleted. The disadvantage is that you cannot use the object directly in
the container, but instead need to use something like shared_ptr
for containers.

2. deal.ii itself implements this features as shown in [2] where they
declare a copy constructor and then have it "assert false".


This, or sometimes we also make it private, so that it can't be called 
from other classes.




I personally prefer the solution 1, since it catches errors are compile
time and seems "cleaner" to me. Is there a reason why I should still
prefer the 2nd solution over the first after C++11?


No. The code pieces you found were all written before C++11 came along. 
(We also don't yet require a compiler that actually understands C++11.) 
In the long run, we should move exactly towards the first solution you 
have above.


Best
 W.

--
You received this message because you are subscribed to the Google Groups "deal.II 
developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dealii-developers+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[dealii-developers] Invalid Copy Constructor vs (Deleted Copy Constructor and Shared Pointer)

2016-08-09 Thread Jayesh Badwaik
Hi,

I am trying to write a grid from scratch and have been looking towards 
deal.ii for guidance on various design decisions and my question is related 
to one such design decision. 

I want to decide what to do with the copy constructor of the grid. 
1. With the c++11, we can use the delete keyword for the copy constructor 
[1]. The advantage is the copy constructor is "cleanly" deleted. The 
disadvantage is that you cannot use the object directly in the container, 
but instead need to use something like shared_ptr for containers. 

2. deal.ii itself implements this features as shown in [2] where they 
declare a copy constructor and then have it "assert false".  

I personally prefer the solution 1, since it catches errors are compile 
time and seems "cleaner" to me. Is there a reason why I should still prefer 
the 2nd solution over the first after C++11? 

Thank You
--
Cheers
Jayesh

[1] : 
http://en.cppreference.com/w/cpp/language/copy_assignment#Deleted_implicitly-declared_copy_assignment_operator
[2] : 
https://www.dealii.org/8.4.1/doxygen/deal.II/classTriangulation.html#ac915084b738c83c836e2e26d439c4c67

-- 
You received this message because you are subscribed to the Google Groups 
"deal.II developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dealii-developers+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.