[DuMuX] Task 330: Handbook refers to user wiki which will be shut down
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Christoph Grüninger (gruenich) Attached to Project - DuMuX Summary - Handbook refers to user wiki which will be shut down Task Type - DuMuX day Category - General Status - New Assigned To - Operating System - Unspecified Severity - Low Priority - High Reported Version - 2.9 Due in Version - 2.10 Due Date - Undecided Details - Our handbook refers to the Dune user wiki which will be shut down Oktober 4th. We have to check whether we want to remove the pointer or put some of the content back to the handbook. More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=330 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 329: Suspicious calculation in air's gasViscosity
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Christoph Grüninger (gruenich) Attached to Project - DuMuX Summary - Suspicious calculation in air's gasViscosity Task Type - Bug Report Category - Material framwork Status - New Assigned To - Operating System - Unspecified Severity - High Priority - Normal Reported Version - 2.9 Due in Version - 2.10 Due Date - Undecided Details - in dumux/material/components/air.hh:134 the dipole moment is set to 0. This leads to a pointless (probably optimized away) calculation of mu_r4. Either we remove the computation or fix the value of the dipole moment. This error is with us since the initial creation of the file in 2012… Code excerpt: const Scalar dipole = 0.0; // dipole moment [debye] Scalar mu_r4 = 131.3 * dipole / std::sqrt(Vc * Tc); mu_r4 *= mu_r4; mu_r4 *= mu_r4; Scalar Fc = 1 - 0.2756*omega + 0.059035*mu_r4; More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=329 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. ___ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 280: Does 2pnc replaces 2p2c
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#280 - Does 2pnc replaces 2p2c User who did this - Johannes Hommel (Joh_Ho) -- I think during the discussion in July, we did not think about the performance. I agree that we should test the performance before we make a final decision. -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=280#comment711 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 280: Does 2pnc replaces 2p2c
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#280 - Does 2pnc replaces 2p2c User who did this - Timo Koch (timokoch) -- I'm quite sure it is going to be slower. I haven't tested it though. The 2p2c can use a specialized constraint solver in the volume variables that should be more efficient than the more general one needed by the 2pnc. In the interest of keeping this performance benefit I would keep at least the volume variables implementation. The same goes for the variable switch that needs different treatment in both models. The only thing that can be replaced would be the localresidual then. Here I suggest looking into formulating a CompositionalLocalResidual class and an ImmiscibleLocalResidual class that could be used for 1p2c/2p2c/2pnc/3p3c and 1p/2p/3p respectively. I would suggest keeping the 2p2c model, open a separate Flyspray task for the local residual suggestion, and postpone to the next release if noone objects. -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=280#comment710 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. ___ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 328: Use math functions from std:: and allow ADL
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Christoph Grüninger (gruenich) Attached to Project - DuMuX Summary - Use math functions from std:: and allow ADL Task Type - DuMuX day Category - General Status - New Assigned To - Operating System - Unspecified Severity - Medium Priority - Normal Reported Version - 2.9 Due in Version - 2.11 Due Date - Undecided Details - We use std::pow and pow for the power function. It is adviced to use using namespace std; and then just pow. We should discuss an according change of all used math functions. This task arose from a discussion in https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/merge_requests/192 More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=328 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 321: DiffusivityConstantTau unused, rename tau
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#321 - DiffusivityConstantTau unused, rename tau User who did this - Christoph Grüninger (gruenich) Reason for closing: Implemented Additional comments about closing: Property is now called TauTortuosity and has a default value of 0.5 according to Carman, see newly added documentation. More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=321 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 280: Does 2pnc replaces 2p2c
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#280 - Does 2pnc replaces 2p2c User who did this - Christoph Grüninger (gruenich) -- Has someone done performance measurements? Is 2pnc as fast as 2p2c? If it has a negative performance impact, we should fix that or keep 2p2c. -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=280#comment709 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 324: [box/fvelementgeometry] Implement computeGeometries() for prisms
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#324 - [box/fvelementgeometry] Implement computeGeometries() for prisms User who did this - Kilian Weishaupt (Kilian) Reason for closing: Implemented More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=324 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 309: Uninitialised values
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#309 - Uninitialised values User who did this - Kilian Weishaupt (Kilian) Reason for closing: Implemented More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=309 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 323: VTK numbering
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#323 - VTK numbering User who did this - Thomas Fetzer (Thomas Fetzer) Reason for closing: Implemented Additional comments about closing: Implemented in c278897c0176c5656a75a4007347a3881a7b0ae9 More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=323 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 322: remove superfluous "Dumux::"
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#322 - remove superfluous "Dumux::" User who did this - Bernd Flemisch (bernd) Reason for closing: Implemented Additional comments about closing: in 35bf6f1d9d More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=322 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. ___ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 321: DiffusivityConstantTau unused, rename tau
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#321 - DiffusivityConstantTau unused, rename tau User who did this - Christoph Grüninger (gruenich) -- Please have a look at the merge request 181. https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/merge_requests/181 -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=321#comment708 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 315: "using" command interferes with doxygen
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#315 - "using" command interferes with doxygen User who did this - Johannes Hommel (Joh_Ho) Reason for closing: Implemented Additional comments about closing: Implemented in merge request !174 Bernd Flemisch @bernd about 22 hours ago mentioned in commit a53ecd27 More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=315 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. ___ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 327: Release 2.10
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Bernd Flemisch (bernd) Attached to Project - DuMuX Summary - Release 2.10 Task Type - Feature Request Category - General Status - New Assigned To - Johannes Hommel Operating System - Unspecified Severity - Low Priority - Normal Reported Version - 2.9 Due in Version - Undecided Due Date - Undecided Details - Manager: Joh_Ho Scheduled for 30.9. Lecture: Katharina Handbook: Kilian Doxygen: Sina Homepage: Bernd More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=327 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 315: "using" command interferes with doxygen
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#315 - "using" command interferes with doxygen User who did this - Martin Beck (martinb) -- The problem can be solved by moving the "using" command in front of the doxygen description. Example: doxygen description using Base::enthalpy; template ... is replaced by using Base::enthalpy; doxygen description template ... -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=315#comment707 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 326: Migrate Flyspray to gitlab
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Johannes Hommel (Joh_Ho) Attached to Project - DuMuX Summary - Migrate Flyspray to gitlab Task Type - Feature Request Category - General Status - New Assigned To - David Werner Operating System - Unspecified Severity - Critical Priority - Flash Reported Version - 2.9 Due in Version - 2.10 Due Date - Undecided Details - Scripts from the DUNE migration are available and only have to be adapted. More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=326 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 269: Take care of todos
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#269 - Take care of todos User who did this - Johannes Hommel (Joh_Ho) Reason for closing: Implemented More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=269 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 280: Does 2pnc replaces 2p2c
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#280 - Does 2pnc replaces 2p2c User who did this - Johannes Hommel (Joh_Ho) -- 2pnc replaces 2p2c, but property tag an specialisations for 2 components will be kept. -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=280#comment706 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 311: Replace VTKMultiWriter with VTKSequenceWriter provided by Dune
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#311 - Replace VTKMultiWriter with VTKSequenceWriter provided by Dune User who did this - Johannes Hommel (Joh_Ho) Reason for closing: Won't implement More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=311 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. ___ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 316: Gather digital copies of literature used in dumux-stable
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#316 - Gather digital copies of literature used in dumux-stable User who did this - Johannes Hommel (Joh_Ho) Reason for closing: Won't implement More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=316 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. ___ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 316: Gather digital copies of literature used in dumux-stable
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#316 - Gather digital copies of literature used in dumux-stable User who did this - Johannes Hommel (Joh_Ho) -- It is sufficient to provide a proper bibTex entry in doxygen (with DOI or link). -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=316#comment705 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 197: Ba/Ma/PhD data storage
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#197 - Ba/Ma/PhD data storage User who did this - Johannes Hommel (Joh_Ho) Reason for closing: Implemented More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=197 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 316: Gather digital copies of literature used in dumux-stable
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#316 - Gather digital copies of literature used in dumux-stable User who did this - Johannes Hommel (Joh_Ho) -- I suggest that we link this to FS#249 - Names and units in the fluidsystems/components. Whoever checks the material framework (fluidsystem, components etc.) for names and units, may at the same time compile at least a list of the literature cited. With this bibliography, it should be relatively easy to gather the literature. However, we need to discuss where to save the gathered literature, giving access to all who need it, but avoiding any copyright issues. -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=316#comment704 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 197: Ba/Ma/PhD data storage
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#197 - Ba/Ma/PhD data storage User who did this - Johannes Hommel (Joh_Ho) -- Users/PhD students from LH2 can now store large amounts of data within a personal folder on our data-user at /home/aux/data/YourName. In my opinion, we now have enough options for data storage, depending on the importance, purpose and size of the data: - input and output data of simulations connected to papers/theses --> dumux-pub - (experimental) data related to BSc/MSc theses exceeding the input and output data of simulations --> on CD/DVD - large data sets from experiments or other sources that may be of interest for other/later PhD students and researchers (at LH2) --> data user - large data sets which are of no potential interest at all --> why store them? Is there any case that I did not mention? Otherwise I would suggest to close this task. -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=197#comment703 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 325: default to AMGBackend?
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#325 - default to AMGBackend? User who did this - Bernd Flemisch (bernd) -- Why? The AMGBackend should also work without direct solver, shouldn't it? -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=325#comment702 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. ___ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 325: default to AMGBackend?
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#325 - default to AMGBackend? User who did this - Christoph Grüninger (gruenich) -- As a consequence we would require SuperLU or UMFPack from all our users. We can decide on this, but we have to keep this fact in mind. -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=325#comment701 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 280: Does 2pnc replaces 2p2c
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#280 - Does 2pnc replaces 2p2c User who did this - Johannes Hommel (Joh_Ho) -- Quote from some time ago: "This is a task which has to be decided for the release 2.9" As we are planning the release 2.10 and apparently, as there still exists a 2p2c model, we should decide now and document the decision. -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=280#comment700 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. ___ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 325: default to AMGBackend?
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Bernd Flemisch (bernd) Attached to Project - DuMuX Summary - default to AMGBackend? Task Type - Feature Request Category - General Status - New Assigned To - Bernd Flemisch Operating System - Unspecified Severity - Low Priority - Normal Reported Version - 2.9 Due in Version - 2.10 Due Date - Undecided Details - Since we got rid of our self-written parallel linear solvers, the default linear solvers are sequential. This prevents us from doing a parallel run without having to modify the problem file and to recompile. I would prefer to set the default linear solver to the AMGBackend. Not only is it parallel, is also showed the best performance in a recent independent study, at least averaged over a range of models, discretizations and grid sizes. More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=325 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 324: [box/fvelementgeometry] Implement computeGeometries() for prisms
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Kilian Weishaupt (Kilian) Attached to Project - DuMuX Summary - [box/fvelementgeometry] Implement computeGeometries() for prisms Task Type - Bug Report Category - General Status - New Assigned To - Timo Koch Operating System - Unspecified Severity - Medium Priority - Normal Reported Version - 2.9 Due in Version - Undecided Due Date - Undecided Details - computeGeometries() so far only works for tetrahedrons and hexahedrons. Using the box method on grids with prismatic elements is not yet possible. More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=324 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 268: gstat development
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#268 - gstat development User who did this - Thomas Fetzer (Thomas Fetzer) Reason for closing: Implemented Additional comments about closing: Has been implemented in MR 152 More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=268 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 323: VTK numbering
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#323 - VTK numbering User who did this - Timo Koch (timokoch) -- If I recall correctly paraview handles that just fine. And dune uses numbering starting from 0 too. Someone would need to change the vtu numbers in all the CMakeLists.txt in the tests. -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=323#comment699 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 323: VTK numbering
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#323 - VTK numbering User who did this - Bernd Flemisch (bernd) -- I'm all in favor for this. One should check if Paraview indeed takes the ...0 file as the first one if all the vtu files are opened at once (not the pvd file). -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=323#comment698 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. ___ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 323: VTK numbering
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Thomas Fetzer (Thomas Fetzer) Attached to Project - DuMuX Summary - VTK numbering Task Type - Bug Report Category - General Status - New Assigned To - Thomas Fetzer Operating System - Unspecified Severity - Low Priority - Normal Reported Version - Git Due in Version - Undecided Due Date - Undecided Details - I would propose to change the numbering of vtks. For me it makes more sense if the initial solution gets the index 0. This would have the advantage that the index of the vtk corresponds to the time step number. Or is there a reason why the VTK numbering is as it is? More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=323 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 306: Unify and generalize diffusive fluxes
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#306 - Unify and generalize diffusive fluxes User who did this - Alexander Kissinger (alexk) -- A unified dispersion model similar to the one available in the 1p2c model should also be considered in a similar fashion as the diffusion model. -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=306#comment697 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 301: Solution dependent spatial parameters
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#301 - Solution dependent spatial parameters User who did this - Timo Koch (timokoch) -- Does this mean that the permeability in the local residual is taken from volume variables? always? And call an empty material law? This would mean that we always copy the permeability into the volume variables on update also for models (95%) that don't use solution dependent spatial params. -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=301#comment696 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. ___ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 301: Solution dependent spatial parameters
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#301 - Solution dependent spatial parameters User who did this - Alexander Kissinger (alexk) -- At the Dumux meeting today we discussed this topic: A favored implementation is to implement solution dependent spatial parameters as fluid-matrix-interactions, which is basically what they are. This means that within the volume-variables a material law for permeabiliy, porosity etc is called which gets the current volume variables and the spatial parameters as an argument. In this way no direct calls to the spatial parameters from the volume variables would be necessary anymore. The material laws could then be set with a property similar to the capillary pressure or the effective heat conductivity. If the user wants to implement his own material law he could do so on the material level without having to touch the model level. -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=301#comment695 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 275: Easier handling of boundary conditions and sources
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#275 - Easier handling of boundary conditions and sources User who did this - Bernd Flemisch (bernd) -- I somehow would like to get a python interface in the long run. Most likely, something in this direction will be done in one of Dune's Google Summer of Code projects and we can profit from the experiences made there. There's no need to rush this. "Somehow" means that I also share Christoph's opinion. I think that a Python interface will not be of too much use for our PhD students. Maybe even a burden because some of them additionally have to learn Python. On the other hand, I can imagine quite a benefit for persons who only want to "use" Dumux, whatever that means. And that would include (some/most of) our Bachelor and Master students. As an intermediate step, I was thinking of defining some common boundary condition types like "no flow", "fully saturated hydrostatic", "all constant Dirichlet values", ... and providing a possibility to set them for every dof / scvf or also for something like the top/bottom/front... of the domain. I'm unsure if this is worth the effort. -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=275#comment694 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. ___ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 275: Easier handling of boundary conditions and sources
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#275 - Easier handling of boundary conditions and sources User who did this - Christoph Grüninger (gruenich) -- Introducing another language (beside C++, C++ templates, and if you want property system, input files and CMake) increases the complexity. I am not sure whether the benefit does outweigh this. -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=275#comment693 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 275: Easier handling of boundary conditions and sources
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#275 - Easier handling of boundary conditions and sources User who did this - Timo Koch (timokoch) -- Yes. Point sources make it easier to specify e.g. a simple well now. However, this was also related to making it possible to specify sources and boundary conditions through the input file. Looking into this I think the only practically feasible way is to use a Python interface. As an example of simple to more complex C++ interaction with Python see e.g. dune-fufem/dune/fufem/test/dunepythontest.cc. (seems to be fairly easy to use and implement) The reason for this is that for a flexible control of the boundary conditions and sources we really need to specify functions and maybe use if/else constructs in the input file in order to do more than already available (set constant values, set a switch choosing at runtime between different implementations of the boundary conditions function). If someone has a good HIWI I would give that a try. What do other people think? -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=275#comment692 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 322: remove superfluous "Dumux::"
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#322 - remove superfluous "Dumux::" User who did this - Timo Koch (timokoch) -- I think the Dune:: prefix here was actually wrong / less general. It think it doesn't work with grids placed in another namespace than Dune because Dune intended to make that work through ADL. Nevertheless we should probably make it consistent. I actually find your first example more readable. Our problem are always implemented in their own header which we put in the Dumux namespace. In a cc file however I would personally not put anything in a namespace and always use the correct namespace specifier. As problem and spatial params are kind of our cc file extensions I would personally make it clear there where things come from, although it should be already clear given the namespace... No strong opposition here. I think we can discuss this and execute changes at the next Dumux day? -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=322#comment691 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. ___ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 322: remove superfluous "Dumux::"
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#322 - remove superfluous "Dumux::"
User who did this - Bernd Flemisch (bernd)
--
Recently, we merged
https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/merge_requests/65
This change affected 138 files. It removed the "Dune::" from the "elements" and
"intersections" functions. The only argument given was that the compiler is
able to do it. While I liked that change, it is much more obscure than the one
proposed now, since we now call a function from within a namespace "Dumux" that
is out of another namespace "Dune" without qualifying it like this.
I really see no reason why I should use the namespace qualifier if I want to
use a name from the very namespace that I'm in, apart from avoiding technical
ambiguities. We also never say
namespace Dumux {
...
class LensProblem : public Dumux::ImplicitPorousMediaProblem
...
}
--
More information can be found at the following URL:
http://www.dumux.org/flyspray/index.php?do=details&task_id=322#comment690
You are receiving this message because you have requested it from the Flyspray
bugtracking system. If you did not expect this message or don't want to
receive mails in future, you can change your notification settings at the URL
shown above.
___
Dumux mailing list
Dumux@listserv.uni-stuttgart.de
https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 322: remove superfluous "Dumux::"
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#322 - remove superfluous "Dumux::" User who did this - Bernd Flemisch (bernd) -- We also have files where it is mixed. For example, in test/porousmediumflow/2p/implicit/lensproblem.hh, every property setting until line 94 gets a "Dumux::", everything below doesn't. We should at least make it consistent throughout a file. -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=322#comment689 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 322: remove superfluous "Dumux::"
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#322 - remove superfluous "Dumux::"
User who did this - Bernd Flemisch (bernd)
--
Compare
typedef Dumux::FluidSystems::LiquidPhase > type;
with
typedef FluidSystems::LiquidPhase > type;
or
SET_TYPE_PROP(OnePNIConductionProblem, Fluid,
Dumux::FluidSystems::LiquidPhase >);
with
SET_TYPE_PROP(OnePNIConductionProblem, Fluid,
FluidSystems::LiquidPhase >);
To me, the lines without "Dumux::" are quite a bit better to read. I also would
say that most names in Dumux that aren't qualified by "Dune::" or "std::" are
from the namespace Dumux.
If removing yields an error, the occurrence is not superfluous.
--
More information can be found at the following URL:
http://www.dumux.org/flyspray/index.php?do=details&task_id=322#comment688
You are receiving this message because you have requested it from the Flyspray
bugtracking system. If you did not expect this message or don't want to
receive mails in future, you can change your notification settings at the URL
shown above.
___
Dumux mailing list
Dumux@listserv.uni-stuttgart.de
https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 320: Implementation of dispersion in 1p2c not correct for cell centred disc.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#320 - Implementation of dispersion in 1p2c not correct for cell centred disc. User who did this - Timo Koch (timokoch) -- In the cc method the velocity is only approximated as normal velocity on the face (TPFA). The velocity is not given on the cell centers. The cell velocity we compute is an interpolated one. I don't know right now to compute the dispersion tensor on the face correctly so this is just a comment. -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=320#comment687 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. ___ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 321: DiffusivityConstantTau unused, rename tau
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#321 - DiffusivityConstantTau unused, rename tau User who did this - Timo Koch (timokoch) -- Isn't it a spatial param, thus better in group SpatialParams? Technically it's probably also not reasonable to be a property because it depends on the material so it should be different (theoretically if values are available) and thus be defined in the Spatialparams. Are there other params like this? Maybe a turtuosity function that returns a default in the base spatialparams class is an option? -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=321#comment686 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. ___ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 322: remove superfluous "Dumux::"
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#322 - remove superfluous "Dumux::" User who did this - Timo Koch (timokoch) -- I think it actually makes things more clear. It's then obvious that it comes from the Dumux namespace. I wouldn't go so far as to make it mandatory and not operate in namespace Dumux but I don't think it clutters the code. Also I experienced some difficulties with certain versions of GCC where something like typedef BoundingBoxTree BoundingBoxTree; threw an error saying I redefine the symbol BoundingBoxTree with another meaning while typedef Dumux::BoundingBoxTree BoundingBoxTree; worked just fine. -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=322#comment685 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 322: remove superfluous "Dumux::"
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#322 - remove superfluous "Dumux::" User who did this - Christoph Grüninger (gruenich) -- Is it worth the effort? Someone has to do it, it clutters the history of changed lines and sometimes it is even helpful. We could think about not adding to to new files, but I wouldn't do a massive removal of them. -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=322#comment684 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. ___ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 322: remove superfluous "Dumux::"
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Bernd Flemisch (bernd) Attached to Project - DuMuX Summary - remove superfluous "Dumux::" Task Type - Feature Request Category - General Status - New Assigned To - Operating System - Unspecified Severity - Low Priority - Normal Reported Version - 2.9 Due in Version - 2.10 Due Date - Undecided Details - There are more than 1000 occurrences of "Dumux::" in the .hh files of Dumux stable. Most, if not all of them, should be superfluous. I propose to delete those superfluous occurrences. More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=322 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 321: DiffusivityConstantTau unused, rename tau
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#321 - DiffusivityConstantTau unused, rename tau User who did this - Christoph Grüninger (gruenich) -- Thanks for the hint, tau was defined in the input file, thus my grep missed it. Moving it to "Problem" and renaming it, remains for this task. -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=321#comment683 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. ___ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 321: DiffusivityConstantTau unused, rename tau
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#321 - DiffusivityConstantTau unused, rename tau User who did this - Thomas Fetzer (Thomas Fetzer) -- There is a test in material/fluidmatrixinteractions. I would propose to shift tau to a meaningful group, e.g. SpatialParams or at least to Problem. -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=321#comment682 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 321: DiffusivityConstantTau unused, rename tau
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Christoph Grüninger (gruenich) Attached to Project - DuMuX Summary - DiffusivityConstantTau unused, rename tau Task Type - Bug Report Category - 2p Status - New Assigned To - Christoph Grüninger Operating System - Unspecified Severity - Low Priority - Normal Reported Version - 2.9 Due in Version - 2.10 Due Date - Undecided Details - No test case seems to use DiffusivityConstantTau. Additionally, I propose to rename the property "tau" to "TortuosityTau" or just "Turtuosity", as the former is hardly meaningful or unique. More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=321 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 320: Implementation of dispersion in 1p2c not correct for cell centred disc.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Alexander Kissinger (alexk) Attached to Project - DuMuX Summary - Implementation of dispersion in 1p2c not correct for cell centred disc. Task Type - Bug Report Category - General Status - New Assigned To - Operating System - Unspecified Severity - Low Priority - Normal Reported Version - 2.9 Due in Version - Undecided Due Date - Undecided Details - I noticed that the implementation of dispersion in the 1p2c model may not be correct for applications using the cell centered discretization. The dispersion tensor needs to be evaluated at the interface between two dofs. It requires the velocity at that location. For the Box method this can easily be achieved using the potential gradient evaluated from multiple dofs in the element. For the CC method however the potential gradient calculated currently at the interface only depends on the two opposing dofs (i and j). This will generally not result in the correct velocity. A correct implementation would require an interpolation of the two cell velocities i and j at the interface. Example: Flow parallel to the interface between i and j would result in a zero velocity at the interface as there is no potential gradient between i and j and the velocity component parallel to the interface is not considered. As a result also the transverse dispersion would be zero. More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=320 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 299: Release 2.9
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#299 - Release 2.9 User who did this - Kilian Weishaupt (Kilian) Reason for closing: Implemented More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=299 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 286: Cleanup after introduction of new gridcreator
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#286 - Cleanup after introduction of new gridcreator User who did this - Kilian Weishaupt (Kilian) Reason for closing: Implemented More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=286 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 299: Release 2.9
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#299 - Release 2.9 User who did this - Bernd Flemisch (bernd) -- I created a corresponding merge request 113. -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=299#comment681 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 249: Names and units in the fluidsystems/components
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#249 - Names and units in the fluidsystems/components User who did this - Kilian Weishaupt (Kilian) -- While the material folder has been worked over, there is still work to do in other classes. Might be a potential job for a Hiwi. -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=249#comment680 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 312: Generalize electrochemistry class
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#312 - Generalize electrochemistry class User who did this - Kilian Weishaupt (Kilian) Reason for closing: Implemented Additional comments about closing: Major issues have been fixed and the model will be compatible for 2.9. However, further improvements and generalizations might still be done (e.g., the reaction layer is still restricted to one grid cell). More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=312 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 241: move 2pMINC/dualcontinuum to stable
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#241 - move 2pMINC/dualcontinuum to stable User who did this - Bernd Flemisch (bernd) Reason for closing: Deferred Additional comments about closing: 2pminc has been moved to stable. Currently, there is no interest / are no personal resources to move also the dual continuum model. Re-open if necessary. More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=241 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 299: Release 2.9
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#299 - Release 2.9 User who did this - Christoph Grüninger (gruenich) -- We still ship istl and grid patches for 2.3. Can we either drop them or put them on-top of dune 2.4.1? -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=299#comment679 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 291: How to deal with solutes?
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#291 - How to deal with solutes? User who did this - Kilian Weishaupt (Kilian) Reason for closing: Implemented More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=291 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 319: [MaterialLaws] Generalize EffToAbsLaw, Regularization
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Kilian Weishaupt (Kilian) Attached to Project - DuMuX Summary - [MaterialLaws] Generalize EffToAbsLaw, Regularization Task Type - Feature Request Category - Material framwork Status - New Assigned To - Operating System - Unspecified Severity - Low Priority - Normal Reported Version - Git Due in Version - Undecided Due Date - Undecided Details - It should be possible for the user to use a definition like using MaterialLaw = VanGenuchten The Params should have a default constructor setting the way of regularization and the conversion from absolute to relative quantities. Both procedures could be generalized. The materiallaw gets the absolute value and calls a method to convert it to a relative one (defined in a general class). Similarly a method for regularization defined in a general class is called by the materiallaw itself. This reduces the number of classes required and makes everything more clear. More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=319 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 318: Make base flux variables members private
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Timo Koch (timokoch) Attached to Project - DuMuX Summary - Make base flux variables members private Task Type - Feature Request Category - Implicit models Status - New Assigned To - Operating System - Unspecified Severity - Low Priority - Normal Reported Version - Git Due in Version - Undecided Due Date - Undecided Details - The flux variable base classes contain at least a face index, an fv geometry pointer, and a boundary flag as protected member. These should be private and be accessible only via designated return functions. face() already exists. onBoundary() needs to be added (boundary() would be a better fit to the dune grid interface). fvGeometry_() is not public but needs to be accessible to the deriving classes, thus it probably should be protected. It might be introduced through branch feature/make-flux-vars-default-construbtable soon. More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=318 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 317: More use of copydoc in material
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Alexander Kissinger (alexk) Attached to Project - DuMuX Summary - More use of copydoc in material Task Type - Feature Request Category - Documentation Status - New Assigned To - Operating System - Unspecified Severity - Low Priority - Normal Reported Version - Git Due in Version - Undecided Due Date - Undecided Details - There is still some duplicate doxygen documentation in the material folder, for example the FluidState set-functions all have the same documentation. This could be a task for an upcoming Dumux day or a Hiwi. More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=317 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 289: Fluid Framework Description inside the Handbook
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#289 - Fluid Framework Description inside the Handbook User who did this - Alexander Kissinger (alexk) Reason for closing: Implemented Additional comments about closing: - All relevant information from Fluid Framework was moved to Doxygen (Modules->Material and Fluid Framework) - The handbook section was replaced by a reference to Doxygen More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=289 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. ___ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 252: Change names "decoupled" and "implicit"?
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#252 - Change names "decoupled" and "implicit"? User who did this - Kilian Weishaupt (Kilian) Reason for closing: Implemented More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=252 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 260: Improve/update content of the website
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#260 - Improve/update content of the website User who did this - Christoph Grüninger (gruenich) Reason for closing: Implemented Additional comments about closing: page created. Thanks for these writing the texts. More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=260 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 252: Change names "decoupled" and "implicit"?
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#252 - Change names "decoupled" and "implicit"? User who did this - Kilian Weishaupt (Kilian) -- Renaming in handbook/tutorial done -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=252#comment678 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 308: Doxygen description for different models
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#308 - Doxygen description for different models User who did this - Kilian Weishaupt (Kilian) Reason for closing: Implemented More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=308 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 316: Gather digital copies of literature used in dumux-stable
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Alexander Kissinger (alexk) Attached to Project - DuMuX Summary - Gather digital copies of literature used in dumux-stable Task Type - Feature Request Category - General Status - New Assigned To - Operating System - Unspecified Severity - Low Priority - Normal Reported Version - Git Due in Version - Undecided Due Date - Undecided Details - A lot of literature is being cited within the material framework (fluidsystem, components etc.) Should we gather this literature somewhere, so if in doubt we can always lookup the relations? This could be a potential Hiwi-job. More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=316 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 276: Improve the documentation of the tests
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#276 - Improve the documentation of the tests User who did this - Kilian Weishaupt (Kilian) Reason for closing: Implemented More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=276 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 315: "using" command interferes with doxygen
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Martin Beck (martinb) Attached to Project - DuMuX Summary - "using" command interferes with doxygen Task Type - Bug Report Category - Documentation Status - New Assigned To - Operating System - Unspecified Severity - Medium Priority - Normal Reported Version - Git Due in Version - Undecided Due Date - Undecided Details - While working on an update for the description of some functions of the fluidsystems, I noticed that my changes do not appear in the doxygen. After a bit of investigation, I found out that the "using" command is to be blamed. Apparently, it copies the description of the function, to which the "using" command refers to and ignores the description of the actual function. One example: For the enthalpy function of the brine-air fluid system, the description of the base fluid systems shows up instead of the specific description where some references are provided. So this information is lost and one becomes only aware of if one goes through the source code. More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=315 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 314: test_adaptive2p2c2d has invalid downcast
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Christoph Grüninger (gruenich) Attached to Project - DuMuX Summary - test_adaptive2p2c2d has invalid downcast Task Type - Bug Report Category - General Status - New Assigned To - Operating System - Unspecified Severity - Low Priority - Normal Reported Version - Git Due in Version - 2.10 Due Date - Undecided Details - test_adaptive2p2c2d with undefined behavior sanitizer gives an error about an illegal cast: dumux/dumux/porousmediumflow/sequential/impetproblem.hh:836:15: runtime error: downcast of address 0x7ffe0d58ba10 which does not point to an object of type 'Adaptive2p2c2d' 0x7ffe0d58ba10: note: object has invalid vptr 00 00 00 00 00 00 00 00 00 00 00 00 78 50 aa 31 d9 7f 00 00 60 e6 7e 03 00 00 00 00 00 00 00 00 ^~~ invalid vptr More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=314 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. ___ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 313: test_adaptive2p2c2d.cc triggers has duplicate condition
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Christoph Grüninger (gruenich)
Attached to Project - DuMuX
Summary - test_adaptive2p2c2d.cc triggers has duplicate condition
Task Type - Bug Report
Category - Decoupled models
Status - New
Assigned To -
Operating System - Unspecified
Severity - Low
Priority - Normal
Reported Version - Git
Due in Version - 2.10
Due Date - Undecided
Details - GCC 6 with -Wduplicated-cond emits the following warning. Having a
look into the code, it seems like a real bug to me.
In file included from
/temp/gruenich/dune/test241/dumux/dumux/porousmediumflow/2p2c/sequential/fv3dpressureadaptive.hh:36:0,
from
/temp/gruenich/dune/test241/dumux/dumux/porousmediumflow/2p2c/sequential/adaptiveproperties.hh:68,
from
/temp/gruenich/dune/test241/dumux/test/porousmediumflow/2p2c/sequential/test_adaptive2p2c2dproblem.hh:36,
from
/temp/gruenich/dune/test241/dumux/test/porousmediumflow/2p2c/sequential/test_adaptive2p2c2d.cc:26:
/temp/gruenich/dune/test241/dumux/dumux/porousmediumflow/2p2c/sequential/fvmpfal3dinteractionvolumecontaineradaptive.hh:
In member function ‘int
Dumux::FvMpfaL3d2P2CInteractionVolumeContainerAdaptive::getMpfaCase2or4cells(const
IntersectionIterator&,
Dumux::FvMpfaL3d2P2CInteractionVolumeContainerAdaptive::InteractionVolume&,
bool&)’:
/temp/gruenich/dune/test241/dumux/dumux/porousmediumflow/2p2c/sequential/fvmpfal3dinteractionvolumecontaineradaptive.hh:496:18:
warning: duplicated ‘if’ condition [-Wduplicated-cond]
else if(mapJ== 3)
^~
/temp/gruenich/dune/test241/dumux/dumux/porousmediumflow/2p2c/sequential/fvmpfal3dinteractionvolumecontaineradaptive.hh:492:13:
note: previously used here
if (mapJ== 3){
^~
More information can be found at the following URL:
http://www.dumux.org/flyspray/index.php?do=details&task_id=313
You are receiving this message because you have requested it from the Flyspray
bugtracking system. If you did not expect this message or don't want to
receive mails in future, you can change your notification settings at the URL
shown above.
_______
Dumux mailing list
Dumux@listserv.uni-stuttgart.de
https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 263: Don't build executables on make test
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#263 - Don't build executables on make test User who did this - Christoph Grüninger (gruenich) Reason for closing: Deferred Additional comments about closing: We ask users to use Dune 2.4. We prefer the bahvior we get with Dune 2.4. If someone uses Dune 3.0, it's the users duty to know how to is handled by Dune 3.0. More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=263 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. ___ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 260: Improve/update content of the website
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#260 - Improve/update content of the website User who did this - Christoph Grüninger (gruenich) -- * introduce new category "Dumux module" * sub pages are stable, devel and lecture * stable contains link to GitLab -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=260#comment677 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. ___ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 260: Improve/update content of the website
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#260 - Improve/update content of the website User who did this - Christoph Grüninger (gruenich) -- Should we add the build-system documentation generated with Sphinx? This would include all functions and macros from all dependencies (core modules, PDELab, etc.). -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=260#comment676 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 307: Automatically save restart file before simulation breaks down
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#307 - Automatically save restart file before simulation breaks down User who did this - Kilian Weishaupt (Kilian) Reason for closing: Implemented More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=307 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 305: calculation of derivatives for cap. and rel. perm functions
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#305 - calculation of derivatives for cap. and rel. perm functions User who did this - Kilian Weishaupt (Kilian) Reason for closing: Implemented More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=305 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 309: Uninitialised values
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#309 - Uninitialised values User who did this - Kilian Weishaupt (Kilian) -- The dune-alugrid related issues seem to be fixed (https://gitlab.dune-project.org/extensions/dune-alugrid/issues/3#note_14244) However, valgrind still yields errors at other test, e.g. test_boxmpncthermalnonequil -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=309#comment675 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 252: Change names "decoupled" and "implicit"?
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#252 - Change names "decoupled" and "implicit"? User who did this - Kilian Weishaupt (Kilian) -- The renaming must also be considered in the handbook / tutorial! -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=252#comment674 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 305: calculation of derivatives for cap. and rel. perm functions
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#305 - calculation of derivatives for cap. and rel. perm functions User who did this - Timo Koch (timokoch) -- Why throw something. Can't they get deprecated? -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=305#comment673 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. ___ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 305: calculation of derivatives for cap. and rel. perm functions
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#305 - calculation of derivatives for cap. and rel. perm functions User who did this - Kilian Weishaupt (Kilian) -- I have changed dsw to dswe. No changes to tests ect. had to be made because dx_dsw is still available in the effToAbsLaw. The only problem that might occur is if someone still uses dx_dsw without using the effToAbsLaw. Should we leave to old functions in Brookscorey and VanGenuchten and let them return a DUNE_Throw? Might be a bit confusing and messy, though. -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=305#comment672 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 312: Generalize electrochemistry class
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#312 - Generalize electrochemistry class User who did this - Timo Koch (timokoch) -- This won't work after the 2.9 release because of the removal of the CubeGridCreator... -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=312#comment671 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. ___ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 312: Generalize electrochemistry class
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Timo Koch (timokoch) Attached to Project - DuMuX Summary - Generalize electrochemistry class Task Type - Feature Request Category - Material framwork Status - New Assigned To - Operating System - Unspecified Severity - Low Priority - Normal Reported Version - Git Due in Version - Undecided Due Date - Undecided Details - The electrochemistry is currently implemented as a reaction source term but only works for * sources on the boundary * box models * structured 2d grid (it reads the deprecated UpperRightX, NumCellsX,...) More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=312 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 298: FluidState and Property System
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#298 - FluidState and Property System User who did this - Kilian Weishaupt (Kilian) Reason for closing: Implemented More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=298 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 298: FluidState and Property System
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#298 - FluidState and Property System User who did this - Kilian Weishaupt (Kilian) -- Can't find the fluidstate property in the decoupled models. Has the commit been pushed to master? -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=298#comment670 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. ___ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 309: Uninitialised values
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#309 - Uninitialised values User who did this - Kilian Weishaupt (Kilian) -- At least some of the problems seem to be caused by dune-alugrid. Running dune-alugrid/build-cmake/examples/testEfficiency> valgrind ./main_ball_eff yields a conditional jump over unitialized values. Bernd has reported this bug to the developers of dune-alugrid. MemorySanitizer does only work with prepared libraries. libstdc++ is not prepared, thus MemorySanitizer is not useful for us (causing false positives). http://stackoverflow.com/a/20784130 -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=309#comment669 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. ___ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 289: Fluid Framework Description inside the Handbook
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#289 - Fluid Framework Description inside the Handbook User who did this - Alexander Kissinger (alexk) -- The function mergeing could be done by a Hiwi. Any canditates? -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=289#comment668 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 269: Take care of todos
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#269 - Take care of todos User who did this - Kilian Weishaupt (Kilian) -- majority of todos in porousmediumflow and material are unlikely to be ever implemented we should take care of all others, especially the "please doc me" todos -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=269#comment667 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. ___ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 311: Replace VTKMultiWriter with VTKSequenceWriter provided by Dune
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Timo Koch (timokoch) Attached to Project - DuMuX Summary - Replace VTKMultiWriter with VTKSequenceWriter provided by Dune Task Type - Feature Request Category - General Status - New Assigned To - Timo Koch Operating System - Unspecified Severity - Low Priority - Normal Reported Version - Git Due in Version - Undecided Due Date - Undecided Details - The dune implementation is much easier to handle and upstream maintained. If all the functions are available with the Dune VTKWriter we can remove ours. More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=311 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 289: Fluid Framework Description inside the Handbook
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#289 - Fluid Framework Description inside the Handbook User who did this - Alexander Kissinger (alexk) -- The general parts (description of fluidstate, fluidsystem etc.) have been shifted to doxygen and have been placed in the appropriate group descriptions. The functions remain to be merged with the doxygen function description as both the existing function documentation in doxygen and the one in the handbook are different. This may take some more time. -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=289#comment666 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 276: Improve the documentation of the tests
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#276 - Improve the documentation of the tests User who did this - Beatrix Becker (Beatrix) -- DumuxDay Feb 2: All features are summarized in a table (sequential, implicit, freeflow, materiallaw, multidomain). Part of the table is already online (doxygen), only sequential missing. -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=276#comment665 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 303: beautify README
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#303 - beautify README User who did this - Timo Koch (timokoch) Reason for closing: Implemented Additional comments about closing: Changelog was already written in markdown just renamed it finished this task with commit 3a38cf0d More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=303 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 304: Remove TypeTags ExplicitModel and ImplicitModel
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#304 - Remove TypeTags ExplicitModel and ImplicitModel User who did this - Timo Koch (timokoch) Reason for closing: Implemented Additional comments about closing: Implemented in commit 10796c01 More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=304 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 298: FluidState and Property System
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#298 - FluidState and Property System User who did this - Beatrix Becker (Beatrix) -- Already done for all sequential models at the DumuxDay on February 2 -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=298#comment664 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 282: replace alberta with dune-foamgrid
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#282 - replace alberta with dune-foamgrid User who did this - Timo Koch (timokoch) Reason for closing: Implemented Additional comments about closing: Implemented in commit d74539ca. More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=282 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 303: beautify README
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#303 - beautify README User who did this - Christoph Grüninger (gruenich) -- Done for dumux-lecture. Done for dumux-stable except CHANGELOG, I would mandate a Hiwi to do so. -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=303#comment663 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 263: Don't build executables on make test
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#263 - Don't build executables on make test User who did this - Christoph Grüninger (gruenich) -- With Dune 3.0: make does nothing, make build_tests builds the tests but only in the root directory With Dune 2.4: make does nothing in root, make in test builds the tests recursively With Dune 2.3: no longer supported We can mimic the 3.0 behavior in 2.4 similar to what dune-multidomain 2.4 does. Is this desired? -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=263#comment662 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. ___ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 211: Convenience functions should always be used in fluxVars
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#211 - Convenience functions should always be used in fluxVars User who did this - Kilian Weishaupt (Kilian) Reason for closing: Implemented More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=211 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
[DuMuX] Task 211: Convenience functions should always be used in fluxVars
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#211 - Convenience functions should always be used in fluxVars User who did this - Kilian Weishaupt (Kilian) -- The functions have been implemented everywhere except dumux/porousmediumflow/implicit/darcyfluxvariables.hh dumux/porousmediumflow/implicit/forchheimerfluxvariables.hh dumux/material/chemistry/electrochemistry/electrochemistry.hh dumux/io/plotoverline2d.hh Do to the nature of these classes, convenience functions will not be used there. -- More information can be found at the following URL: http://www.dumux.org/flyspray/index.php?do=details&task_id=211#comment661 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. _______ Dumux mailing list Dumux@listserv.uni-stuttgart.de https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
