From rene.gassmoeller at mailbox.org Mon Oct 2 13:15:16 2017 From: rene.gassmoeller at mailbox.org (Rene Gassmoeller) Date: Mon, 02 Oct 2017 20:15:16 -0000 Subject: [aspect-devel] ASPECT Newsletter #40 Message-ID: <20171002201120.39FBEAC2676@geodynamics.org> Hello everyone! This is ASPECT newsletter #40. It automatically reports recently merged features and discussions about the ASPECT mantle convection code. ## Below you find a list of recently proposed or merged features: #1948: Move particle serialization into ParticleHandler (proposed by gassmoeller) https://github.com/geodynamics/aspect/pull/1948 #1947: add doc/modules/changes.h to .gitignore (proposed by tjhei; merged) https://github.com/geodynamics/aspect/pull/1947 #1946: move plugin_graph files (proposed by tjhei; merged) https://github.com/geodynamics/aspect/pull/1946 #1945: particle doxygen fixes (proposed by tjhei; merged) https://github.com/geodynamics/aspect/pull/1945 #1944: fix manual compilation & update parameters (proposed by tjhei; merged) https://github.com/geodynamics/aspect/pull/1944 #1943: Boundary composition function (proposed by gassmoeller; merged) https://github.com/geodynamics/aspect/pull/1943 #1942: Fix particle serialization (proposed by gassmoeller; merged) https://github.com/geodynamics/aspect/pull/1942 #1941: Add support for natural coordinates to geometry models (proposed by MFraters) https://github.com/geodynamics/aspect/pull/1941 #1940: Fix for the Newton switch tolerance (proposed by MFraters; merged) https://github.com/geodynamics/aspect/pull/1940 #1939: WIP: fix Newton SPD debug test. (proposed by MFraters) https://github.com/geodynamics/aspect/pull/1939 #1938: optimalisation of compute current constraints in the Newton solver. (proposed by MFraters; merged) https://github.com/geodynamics/aspect/pull/1938 #1937: Fix some warnings and a bug (proposed by gassmoeller; merged) https://github.com/geodynamics/aspect/pull/1937 #1935: Fix particle hdf5 output compling on a machine which has no hdf5 installed (proposed by MFraters; merged) https://github.com/geodynamics/aspect/pull/1935 #1934: Change shared pointer of melt in simulator_access to unique pointer. (proposed by MFraters; merged) https://github.com/geodynamics/aspect/pull/1934 #1933: Fix for deal 90 pre (proposed by gassmoeller; merged) https://github.com/geodynamics/aspect/pull/1933 #1932: include plugin code in tests instead of copying it (proposed by jdannberg; merged) https://github.com/geodynamics/aspect/pull/1932 #1930: update convection box cookbook (proposed by jdannberg; merged) https://github.com/geodynamics/aspect/pull/1930 #1929: Adjust particle interfaces (proposed by gassmoeller; merged) https://github.com/geodynamics/aspect/pull/1929 #1916: fix for porosity initial composition plugin (proposed by jdannberg; merged) https://github.com/geodynamics/aspect/pull/1916 #1913: Improve particle handler (proposed by gassmoeller; merged) https://github.com/geodynamics/aspect/pull/1913 #1911: Add new developers (proposed by gassmoeller; merged) https://github.com/geodynamics/aspect/pull/1911 #1882: A new boundary temperature plugin (proposed by SiqiZhang; merged) https://github.com/geodynamics/aspect/pull/1882 #1878: Allow prescribed velocities with locally conservative discretization. (proposed by maxrudolph; merged) https://github.com/geodynamics/aspect/pull/1878 #1707: Newton merge 5: adding the keystone to get access to the Newton pipeline (proposed by MFraters; merged) https://github.com/geodynamics/aspect/pull/1707 ## And this is a list of recently opened or closed discussions: #1936: quick_mpi test not working for deal.ii9.0pre (opened) https://github.com/geodynamics/aspect/issues/1936 #1931: prescribed velocity tests use copies of cookbook plugins instead of including them (opened and closed) https://github.com/geodynamics/aspect/issues/1931 #1924: update convection box cookbook (closed) https://github.com/geodynamics/aspect/issues/1924 #1907: make the cell object input argument in the constructor of material models inputs a reference instead of a pointer (closed) https://github.com/geodynamics/aspect/issues/1907 #1831: Random "Assertion `curr_LID!=-1' failed" error (closed) https://github.com/geodynamics/aspect/issues/1831 A list of all major changes since the last release can be found at https://aspect.dealii.org/doc/doxygen/changes_current.html. Thanks for being part of the community! Let us know about questions, problems, bugs or just share your experience by writing to aspect-devel at geodynamics.org, or by opening issues or pull requests at https://www.github.com/geodynamics/aspect. Additional information can be found at https://aspect.dealii.org/, and https://geodynamics.org/cig/software/aspect/. -------------- next part -------------- An HTML attachment was scrubbed... URL: From rene.gassmoeller at mailbox.org Wed Oct 18 11:00:10 2017 From: rene.gassmoeller at mailbox.org (Rene Gassmoeller) Date: Wed, 18 Oct 2017 18:00:10 -0000 Subject: [aspect-devel] ASPECT Newsletter #41 Message-ID: <20171018175605.DEAB3AC23B8@geodynamics.org> Hello everyone! This is ASPECT newsletter #41. It automatically reports recently merged features and discussions about the ASPECT mantle convection code. ## Below you find a list of recently proposed or merged features: #1958: Only filter hdf5 output for continuous elements (proposed by gassmoeller; merged) https://github.com/geodynamics/aspect/pull/1958 #1957: [WIP] Use deal.II particle functionality (proposed by gassmoeller) https://github.com/geodynamics/aspect/pull/1957 #1956: Fix some typos (proposed by anne-glerum; merged) https://github.com/geodynamics/aspect/pull/1956 #1955: Remove assert because initial topo is incorporated into pull_back(point) (proposed by anne-glerum; merged) https://github.com/geodynamics/aspect/pull/1955 #1954: Update error messages (proposed by anne-glerum; merged) https://github.com/geodynamics/aspect/pull/1954 #1953: Assert radial gravity model for box geometry models. (proposed by MFraters; merged) https://github.com/geodynamics/aspect/pull/1953 #1952: Fix depth functions for initial topography (proposed by MFraters) https://github.com/geodynamics/aspect/pull/1952 #1951: add explicit instantiation of convert_point_to_array and convert_array_to_point (proposed by MFraters; merged) https://github.com/geodynamics/aspect/pull/1951 #1949: Add harmonic average particle interpolation scheme (proposed by hlokavarapu) https://github.com/geodynamics/aspect/pull/1949 #1948: Move particle serialization into ParticleHandler (proposed by gassmoeller; merged) https://github.com/geodynamics/aspect/pull/1948 ## And this is a list of recently opened or closed discussions: #1950: ellipsoidal chunk push and pull functions (opened) https://github.com/geodynamics/aspect/issues/1950 A list of all major changes since the last release can be found at https://aspect.dealii.org/doc/doxygen/changes_current.html. Thanks for being part of the community! Let us know about questions, problems, bugs or just share your experience by writing to aspect-devel at geodynamics.org, or by opening issues or pull requests at https://www.github.com/geodynamics/aspect. Additional information can be found at https://aspect.dealii.org/, and https://geodynamics.org/cig/software/aspect/. -------------- next part -------------- An HTML attachment was scrubbed... URL: From lev.karatun at gmail.com Wed Oct 18 19:57:32 2017 From: lev.karatun at gmail.com (Lev Karatun) Date: Wed, 18 Oct 2017 22:57:32 -0400 Subject: [aspect-devel] Dynamic topography Message-ID: Hi everyone, I was trying to plot the topography using the output of the Dynamic topography plugin, but in a lot of models it is within 10 meters of zero, even though the min and max topography statistic shows hundreds or even thousands of meters. I was wondering what could be the source of this discrepancy? Does it not make sense to use dynamic topography with a model with a free surface at the top? If so, is there a relatively simple way to get the output of real topography, similar to the dynamic one? Thanks in advance! Best regards, Lev Karatun. -------------- next part -------------- An HTML attachment was scrubbed... URL: From bangerth at colostate.edu Thu Oct 19 07:18:47 2017 From: bangerth at colostate.edu (Wolfgang Bangerth) Date: Thu, 19 Oct 2017 08:18:47 -0600 Subject: [aspect-devel] Dynamic topography In-Reply-To: References: Message-ID: Hi Lev, > I was trying to plot the topography using the output of the Dynamic topography > plugin, but in a lot of models it is within 10 meters of zero, even though the > min and max topography statistic shows hundreds or even thousands of meters. I > was wondering what could be the source of this discrepancy? These are different things (assuming I interpret your question correctly). The topography is something you specify at the initial time as part of the geometry. The "dynamic topography" is something that results from the motion of the fluid underneath at a given time step. It is how the surface would deform in response to the fluid motion if it wasn't rigid. Or are you saying that the topography you output is due to the moving boundary? In that case, if the boundary would move in perfect response to the fluid stress underneath, then the "dynamic topography" computed in each time step would actually be zero, because there are no excess stresses that aren't already accommodated by the displaced surface! Best W. -- ------------------------------------------------------------------------ Wolfgang Bangerth email: bangerth at colostate.edu www: http://www.math.colostate.edu/~bangerth/ From heister at clemson.edu Thu Oct 19 09:50:16 2017 From: heister at clemson.edu (Timo Heister) Date: Thu, 19 Oct 2017 12:50:16 -0400 Subject: [aspect-devel] Dynamic topography In-Reply-To: References: Message-ID: > Or are you saying that the topography you output is due to the moving > boundary? In that case, if the boundary would move in perfect response to > the fluid stress underneath, then the "dynamic topography" computed in each > time step would actually be zero, because there are no excess stresses that > aren't already accommodated by the displaced surface! To add to Wolfgang's reply: This is basically how the free surface implementation works, we compute how much fluid wants to move through the surface and move the surface accordingly. -- Timo Heister http://www.math.clemson.edu/~heister/ From ian.rose at berkeley.edu Thu Oct 19 10:18:16 2017 From: ian.rose at berkeley.edu (Ian Rose) Date: Thu, 19 Oct 2017 10:18:16 -0700 Subject: [aspect-devel] Dynamic topography In-Reply-To: References: Message-ID: A bit of context: I agree that the naming of the "topography" and "dynamic topography" postprocessors are a bit confusing (the distinction is described in the manual, section A.114). They are that way largely for historical reasons, as Jacky and I were working on those at roughly the same time and did not coordinate naming efforts. But yes, what Wolfgang and Timo say is correct: they are measuring different things. With a free surface, you expect the dynamic topgraphy to be near zero, since we are enforcing no-stress boundary conditions there! As to your other question, Lev: the "topography" postprocessor should provide an option to output the full topography, rather than just min/max values. It's just that nobody has put in the work to do the parallel I/O for it. Cheers, Ian On Thu, Oct 19, 2017 at 9:50 AM, Timo Heister wrote: > > Or are you saying that the topography you output is due to the moving > > boundary? In that case, if the boundary would move in perfect response to > > the fluid stress underneath, then the "dynamic topography" computed in > each > > time step would actually be zero, because there are no excess stresses > that > > aren't already accommodated by the displaced surface! > > To add to Wolfgang's reply: > This is basically how the free surface implementation works, we > compute how much fluid wants to move through the surface and move the > surface accordingly. > > > > -- > Timo Heister > http://www.math.clemson.edu/~heister/ > _______________________________________________ > Aspect-devel mailing list > Aspect-devel at geodynamics.org > http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: From judannberg at gmail.com Thu Oct 19 07:21:00 2017 From: judannberg at gmail.com (Juliane Dannberg) Date: Thu, 19 Oct 2017 08:21:00 -0600 Subject: [aspect-devel] Dynamic topography In-Reply-To: References: Message-ID: Hi Lev, The "dynamic topography" postprocessor computes the topography based on the stresses acting on the surface, so if you have a model with a free surface, that will not give you the answer you are looking for. The "topography" postprocessor outputs the minimum and maximum topography, but if you want to know the topography of the free surface at every point in the domain, unfortunately we don't have a postprocessor for that at the moment. So you could either look at the graphical output (if that is sufficient for what you want to do), or implement the postprocessor yourself. We even have an open github issue that describes the problem, and how you would go about implementing this feature: https://github.com/geodynamics/aspect/issues/1270 Best, Juliane Am 10/18/2017 um 8:57 PM schrieb Lev Karatun: > Hi everyone, > > I was trying to plot the topography using the output of the Dynamic > topography plugin, but in a lot of models it is within 10 meters of > zero, even though the min and max topography statistic shows hundreds > or even thousands of meters. I was wondering what could be the source > of this discrepancy? Does it not make sense to use dynamic topography > with a model with a free surface at the top? If so, is there a > relatively simple way to get the output of real topography, similar to > the dynamic one? > > Thanks in advance! > > Best regards, > Lev Karatun. > > > _______________________________________________ > Aspect-devel mailing list > Aspect-devel at geodynamics.org > http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel ---------------------------------------------------------------------- Juliane Dannberg Postdoctoral Fellow, Colorado State University http://www.math.colostate.edu/~dannberg/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From rene.gassmoeller at mailbox.org Thu Oct 19 12:23:46 2017 From: rene.gassmoeller at mailbox.org (Rene Gassmoeller) Date: Thu, 19 Oct 2017 13:23:46 -0600 Subject: [aspect-devel] Dynamic topography In-Reply-To: References: Message-ID: <9527c496-a2d7-68cb-3bd2-05c8a027f675@mailbox.org> As Ian mentioned, unfortunately there is currently no option to do this. There is an open issue for this fact: https://github.com/geodynamics/aspect/issues/1270, and it is on the list of things that 'should be done', but never get done, because there are always more important things to do. If anyone wants to go ahead with this issue, we would be grateful for it :-). Best, Rene On 10/19/2017 11:18 AM, Ian Rose wrote: > A bit of context: I agree that the naming of the "topography" and > "dynamic topography" postprocessors are a bit confusing (the > distinction is described in the manual, section A.114). They are that > way largely for historical reasons, as Jacky and I were working on > those at roughly the same time and did not coordinate naming efforts. > But yes, what Wolfgang and Timo say is correct: they are measuring > different things. With a free surface, you expect the dynamic > topgraphy to be near zero, since we are enforcing no-stress boundary > conditions there! > > As to your other question, Lev: the "topography" postprocessor should > provide an option to output the full topography, rather than just > min/max values. It's just that nobody has put in the work to do the > parallel I/O for it. > > Cheers, > Ian > > > > On Thu, Oct 19, 2017 at 9:50 AM, Timo Heister > wrote: > > > Or are you saying that the topography you output is due to the moving > > boundary? In that case, if the boundary would move in perfect > response to > > the fluid stress underneath, then the "dynamic topography" > computed in each > > time step would actually be zero, because there are no excess > stresses that > > aren't already accommodated by the displaced surface! > > To add to Wolfgang's reply: > This is basically how the free surface implementation works, we > compute how much fluid wants to move through the surface and move the > surface accordingly. > > > > -- > Timo Heister > http://www.math.clemson.edu/~heister/ > > _______________________________________________ > Aspect-devel mailing list > Aspect-devel at geodynamics.org > http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel > > > > > > _______________________________________________ > Aspect-devel mailing list > Aspect-devel at geodynamics.org > http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel -- Rene Gassmoeller http://www.math.colostate.edu/~gassmoel/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From philip.j.heron at durham.ac.uk Thu Oct 19 12:37:58 2017 From: philip.j.heron at durham.ac.uk (HERON, PHILIP J.) Date: Thu, 19 Oct 2017 19:37:58 +0000 Subject: [aspect-devel] Using seismic tomography as an input Message-ID: Hi all, I've had a number of people asking me about using ASPECT with available seismic tomography data - to input seismic data and obtain density and possibly gravity models. I know this is possible for global spherical models (as shown the S20RTS), but is it possible for a 3D cartesian seismic input? Or would this require working on a plug in? Cheers, Phil -------------- next part -------------- An HTML attachment was scrubbed... URL: From jbnaliboff at ucdavis.edu Thu Oct 19 12:53:26 2017 From: jbnaliboff at ucdavis.edu (John Naliboff) Date: Thu, 19 Oct 2017 12:53:26 -0700 Subject: [aspect-devel] Using seismic tomography as an input In-Reply-To: References: Message-ID: <85b6b133-5ac6-36bb-f708-2ae5287c8934@ucdavis.edu> Hi Phil, It certainly is possible. The plugin for S40RTS maps seismic velocity variations to temperature, which are provided as the initial condition. While it make sense to map S40RTS into a spherical coordinate system, it is straightforward to map a seismic velocity model in cartesian coordinates. One simply needs to specify how the geographic coordinates map to a cartesian grid. One can also read in the initial temperature field through the ascii input option (e.g., velocity->temperature are done externally). The user simply has to take into account the formatting requirements for each coordinate system (specified in the documentation) when reading in the ascii data. One can also specify the initial compositional field structure via ascii text files. I've used this method for reading in CRUST1.0 in various coordinate systems. So, lots of options! If one of your colleagues has specific questions or needs to help getting started, please have them contact us! Cheers, John ************************************************* John Naliboff Assistant Project Scientist, CIG Earth & Planetary Sciences Dept., UC Davis On 10/19/2017 12:37 PM, HERON, PHILIP J. wrote: > > Hi all, > > > I've had a number of people asking me about using ASPECT with > available seismic tomography data - to input seismic data and obtain > density and possibly gravity models. I know this is possible for > global spherical models (as shown the S20RTS), but is it possible for > a 3D cartesian seismic input? Or would this require working on a plug in? > > > Cheers, > > > Phil > > > > > > > _______________________________________________ > Aspect-devel mailing list > Aspect-devel at geodynamics.org > http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel -------------- next part -------------- An HTML attachment was scrubbed... URL: From pbremner at ufl.edu Thu Oct 19 14:04:30 2017 From: pbremner at ufl.edu (Bremner,Paul M) Date: Thu, 19 Oct 2017 21:04:30 +0000 Subject: [aspect-devel] Using seismic tomography as an input In-Reply-To: References: Message-ID: Hi Phil, I believe a 3D Cartesian model can be input into the ascii plug-in. I also just want to make sure I understand your purpose correctly, are you hoping to input seismic tomography models for the express purpose of obtaining a density and gravity model? Or are you wanting to simply use the tomography models to feed a density model to ASPECT? I believe that both the S40RTS and ascii plug-ins assign the temperature field in ASPECT, and not the density. For example, in S40RTS the velocity perturbation at a particular point is converted to density perturbation by multiplying a constant scale factor. That value is then multiplied by 1/alpha to get temperature perturbation, which is added to a background temperature for that point. Cheers, Paul ------------------------------ Subject: Digest Footer _______________________________________________ Aspect-devel mailing list Aspect-devel at geodynamics.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.geodynamics.org_cgi-2Dbin_mailman_listinfo_aspect-2Ddevel&d=DwIGaQ&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=Wl19MSBMb4DZXdORUmp5jA&m=IlyCRz3zvOcycd_IMQiBKL7HsdUkdvb1HQwsaicq2-Q&s=iQC22OjEmDV_vdq0wXaZKucakl7GNkgA7aySC5tDJaE&e= ------------------------------ End of Aspect-devel Digest, Vol 71, Issue 4 ******************************************* -------------- next part -------------- An HTML attachment was scrubbed... URL: From lev.karatun at gmail.com Thu Oct 19 20:41:07 2017 From: lev.karatun at gmail.com (Lev Karatun) Date: Thu, 19 Oct 2017 23:41:07 -0400 Subject: [aspect-devel] Dynamic topography In-Reply-To: <9527c496-a2d7-68cb-3bd2-05c8a027f675@mailbox.org> References: <9527c496-a2d7-68cb-3bd2-05c8a027f675@mailbox.org> Message-ID: Thank you everyone for the responses! I kind of realized dynamic topography should be around zero when free surface in enabled, but in reality in some of my models it was not (reaching hundreds and even thousands of meters). I assume it means the errors were high when the surface displacements were calculated? Should I be worried about it? Is there a way to fight it? I tried decreasing the free surface solver tolerance, but it didn't help. Best regards, Lev Karatun. 2017-10-19 15:23 GMT-04:00 Rene Gassmoeller : > As Ian mentioned, unfortunately there is currently no option to do this. > > There is an open issue for this fact: https://github.com/geodynamics > /aspect/issues/1270, and it is on the list of things that 'should be > done', but never get done, because there are always more important things > to do. If anyone wants to go ahead with this issue, we would be grateful > for it :-). > > Best, > > Rene > > On 10/19/2017 11:18 AM, Ian Rose wrote: > > A bit of context: I agree that the naming of the "topography" and "dynamic > topography" postprocessors are a bit confusing (the distinction is > described in the manual, section A.114). They are that way largely for > historical reasons, as Jacky and I were working on those at roughly the > same time and did not coordinate naming efforts. But yes, what Wolfgang and > Timo say is correct: they are measuring different things. With a free > surface, you expect the dynamic topgraphy to be near zero, since we are > enforcing no-stress boundary conditions there! > > As to your other question, Lev: the "topography" postprocessor should > provide an option to output the full topography, rather than just min/max > values. It's just that nobody has put in the work to do the parallel I/O > for it. > > Cheers, > Ian > > > > On Thu, Oct 19, 2017 at 9:50 AM, Timo Heister wrote: > >> > Or are you saying that the topography you output is due to the moving >> > boundary? In that case, if the boundary would move in perfect response >> to >> > the fluid stress underneath, then the "dynamic topography" computed in >> each >> > time step would actually be zero, because there are no excess stresses >> that >> > aren't already accommodated by the displaced surface! >> >> To add to Wolfgang's reply: >> This is basically how the free surface implementation works, we >> compute how much fluid wants to move through the surface and move the >> surface accordingly. >> >> >> >> -- >> Timo Heister >> http://www.math.clemson.edu/~heister/ >> _______________________________________________ >> Aspect-devel mailing list >> Aspect-devel at geodynamics.org >> http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel >> > > > > _______________________________________________ > Aspect-devel mailing listAspect-devel at geodynamics.orghttp://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel > > > -- > Rene Gassmoellerhttp://www.math.colostate.edu/~gassmoel/ > > > _______________________________________________ > Aspect-devel mailing list > Aspect-devel at geodynamics.org > http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: From philip.j.heron at durham.ac.uk Fri Oct 20 01:37:50 2017 From: philip.j.heron at durham.ac.uk (HERON, PHILIP J.) Date: Fri, 20 Oct 2017 08:37:50 +0000 Subject: [aspect-devel] Using seismic tomography as an input In-Reply-To: References: , Message-ID: Hi Paul and John, Thanks for the replies! "are you hoping to input seismic tomography models for the express purpose of obtaining a density and gravity model?" Yes, this is what he is looking to do. Heat flux would be a bonus, too. I've passed on the information and he is going to download Aspect this afternoon. I think this would be really neat if we can get a working example up and running from this. I'll keep you posted and I (or more than likely he) will drop back in with some questions. Thanks again, Phil ________________________________ From: Aspect-devel on behalf of Bremner,Paul M Sent: 19 October 2017 22:04:30 To: aspect-devel at geodynamics.org Subject: Re: [aspect-devel] Using seismic tomography as an input Hi Phil, I believe a 3D Cartesian model can be input into the ascii plug-in. I also just want to make sure I understand your purpose correctly, are you hoping to input seismic tomography models for the express purpose of obtaining a density and gravity model? Or are you wanting to simply use the tomography models to feed a density model to ASPECT? I believe that both the S40RTS and ascii plug-ins assign the temperature field in ASPECT, and not the density. For example, in S40RTS the velocity perturbation at a particular point is converted to density perturbation by multiplying a constant scale factor. That value is then multiplied by 1/alpha to get temperature perturbation, which is added to a background temperature for that point. Cheers, Paul ------------------------------ Subject: Digest Footer _______________________________________________ Aspect-devel mailing list Aspect-devel at geodynamics.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.geodynamics.org_cgi-2Dbin_mailman_listinfo_aspect-2Ddevel&d=DwIGaQ&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=Wl19MSBMb4DZXdORUmp5jA&m=IlyCRz3zvOcycd_IMQiBKL7HsdUkdvb1HQwsaicq2-Q&s=iQC22OjEmDV_vdq0wXaZKucakl7GNkgA7aySC5tDJaE&e= ------------------------------ End of Aspect-devel Digest, Vol 71, Issue 4 ******************************************* -------------- next part -------------- An HTML attachment was scrubbed... URL: From pbremner at ufl.edu Fri Oct 20 06:52:15 2017 From: pbremner at ufl.edu (Bremner,Paul M) Date: Fri, 20 Oct 2017 13:52:15 +0000 Subject: [aspect-devel] Using seismic tomography as an input In-Reply-To: References: Message-ID: Hi John, Phil, Something I've had on my back burner is to add functionality to the S40RTS plug-in (maybe ascii too?) to optionally use the initial density distribution obtained when mapping the seismic velocities to temperature. But perhaps there is a different way of doing this, or maybe the density mapping wasn't used for a reason. Thoughts? - Paul ________________________________ From: Aspect-devel on behalf of aspect-devel-request at geodynamics.org Sent: Friday, October 20, 2017 12:27 AM To: aspect-devel at geodynamics.org Subject: Aspect-devel Digest, Vol 71, Issue 5 Send Aspect-devel mailing list submissions to aspect-devel at geodynamics.org To subscribe or unsubscribe via the World Wide Web, visit https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.geodynamics.org_cgi-2Dbin_mailman_listinfo_aspect-2Ddevel&d=DwIGaQ&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=Wl19MSBMb4DZXdORUmp5jA&m=LL9fug0ZE7qJZzKQjUMkIsvL0aLvN-x7mpaYSYowf0A&s=GClD7drldCjJ0bq0-jgj8K7TClGgOnpUcEYULdN5RCs&e= or, via email, send a message with subject or body 'help' to aspect-devel-request at geodynamics.org You can reach the person managing the list at aspect-devel-owner at geodynamics.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Aspect-devel digest..." Today's Topics: 1. Re: Using seismic tomography as an input (John Naliboff) 2. Re: Using seismic tomography as an input (Bremner,Paul M) 3. Re: Dynamic topography (Lev Karatun) ---------------------------------------------------------------------- Message: 1 Date: Thu, 19 Oct 2017 12:53:26 -0700 From: John Naliboff To: aspect-devel at geodynamics.org Subject: Re: [aspect-devel] Using seismic tomography as an input Message-ID: <85b6b133-5ac6-36bb-f708-2ae5287c8934 at ucdavis.edu> Content-Type: text/plain; charset="windows-1252"; Format="flowed" Hi Phil, It certainly is possible. The plugin for S40RTS maps seismic velocity variations to temperature, which are provided as the initial condition. While it make sense to map S40RTS into a spherical coordinate system, it is straightforward to map a seismic velocity model in cartesian coordinates. One simply needs to specify how the geographic coordinates map to a cartesian grid. One can also read in the initial temperature field through the ascii input option (e.g., velocity->temperature are done externally). The user simply has to take into account the formatting requirements for each coordinate system (specified in the documentation) when reading in the ascii data. One can also specify the initial compositional field structure via ascii text files. I've used this method for reading in CRUST1.0 in various coordinate systems. So, lots of options! If one of your colleagues has specific questions or needs to help getting started, please have them contact us! Cheers, John ************************************************* John Naliboff Assistant Project Scientist, CIG Earth & Planetary Sciences Dept., UC Davis On 10/19/2017 12:37 PM, HERON, PHILIP J. wrote: > > Hi all, > > > I've had a number of people asking me about using ASPECT with > available seismic tomography data - to input seismic data and obtain > density and possibly gravity models. I know this is possible for > global spherical models (as shown the S20RTS), but is it possible for > a 3D cartesian seismic input? Or would this require working on a plug in? > > > Cheers, > > > Phil > > > > > > > _______________________________________________ > Aspect-devel mailing list > Aspect-devel at geodynamics.org > https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.geodynamics.org_cgi-2Dbin_mailman_listinfo_aspect-2Ddevel&d=DwIGaQ&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=Wl19MSBMb4DZXdORUmp5jA&m=LL9fug0ZE7qJZzKQjUMkIsvL0aLvN-x7mpaYSYowf0A&s=GClD7drldCjJ0bq0-jgj8K7TClGgOnpUcEYULdN5RCs&e= -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 2 Date: Thu, 19 Oct 2017 21:04:30 +0000 From: "Bremner,Paul M" To: "aspect-devel at geodynamics.org" Subject: Re: [aspect-devel] Using seismic tomography as an input Message-ID: Content-Type: text/plain; charset="iso-8859-1" Hi Phil, I believe a 3D Cartesian model can be input into the ascii plug-in. I also just want to make sure I understand your purpose correctly, are you hoping to input seismic tomography models for the express purpose of obtaining a density and gravity model? Or are you wanting to simply use the tomography models to feed a density model to ASPECT? I believe that both the S40RTS and ascii plug-ins assign the temperature field in ASPECT, and not the density. For example, in S40RTS the velocity perturbation at a particular point is converted to density perturbation by multiplying a constant scale factor. That value is then multiplied by 1/alpha to get temperature perturbation, which is added to a background temperature for that point. Cheers, Paul ------------------------------ Subject: Digest Footer _______________________________________________ Aspect-devel mailing list Aspect-devel at geodynamics.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.geodynamics.org_cgi-2Dbin_mailman_listinfo_aspect-2Ddevel&d=DwIGaQ&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=Wl19MSBMb4DZXdORUmp5jA&m=IlyCRz3zvOcycd_IMQiBKL7HsdUkdvb1HQwsaicq2-Q&s=iQC22OjEmDV_vdq0wXaZKucakl7GNkgA7aySC5tDJaE&e= ------------------------------ End of Aspect-devel Digest, Vol 71, Issue 4 ******************************************* -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 3 Date: Thu, 19 Oct 2017 23:41:07 -0400 From: Lev Karatun To: "aspect-devel at geodynamics.org" Subject: Re: [aspect-devel] Dynamic topography Message-ID: Content-Type: text/plain; charset="utf-8" Thank you everyone for the responses! I kind of realized dynamic topography should be around zero when free surface in enabled, but in reality in some of my models it was not (reaching hundreds and even thousands of meters). I assume it means the errors were high when the surface displacements were calculated? Should I be worried about it? Is there a way to fight it? I tried decreasing the free surface solver tolerance, but it didn't help. Best regards, Lev Karatun. 2017-10-19 15:23 GMT-04:00 Rene Gassmoeller : > As Ian mentioned, unfortunately there is currently no option to do this. > > There is an open issue for this fact: https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_geodynamics&d=DwIGaQ&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=Wl19MSBMb4DZXdORUmp5jA&m=LL9fug0ZE7qJZzKQjUMkIsvL0aLvN-x7mpaYSYowf0A&s=5TaO9E57deZ5NcMMBpIje94EhzplkyR6wWQPaLXtzOE&e= > /aspect/issues/1270, and it is on the list of things that 'should be > done', but never get done, because there are always more important things > to do. If anyone wants to go ahead with this issue, we would be grateful > for it :-). > > Best, > > Rene > > On 10/19/2017 11:18 AM, Ian Rose wrote: > > A bit of context: I agree that the naming of the "topography" and "dynamic > topography" postprocessors are a bit confusing (the distinction is > described in the manual, section A.114). They are that way largely for > historical reasons, as Jacky and I were working on those at roughly the > same time and did not coordinate naming efforts. But yes, what Wolfgang and > Timo say is correct: they are measuring different things. With a free > surface, you expect the dynamic topgraphy to be near zero, since we are > enforcing no-stress boundary conditions there! > > As to your other question, Lev: the "topography" postprocessor should > provide an option to output the full topography, rather than just min/max > values. It's just that nobody has put in the work to do the parallel I/O > for it. > > Cheers, > Ian > > > > On Thu, Oct 19, 2017 at 9:50 AM, Timo Heister wrote: > >> > Or are you saying that the topography you output is due to the moving >> > boundary? In that case, if the boundary would move in perfect response >> to >> > the fluid stress underneath, then the "dynamic topography" computed in >> each >> > time step would actually be zero, because there are no excess stresses >> that >> > aren't already accommodated by the displaced surface! >> >> To add to Wolfgang's reply: >> This is basically how the free surface implementation works, we >> compute how much fluid wants to move through the surface and move the >> surface accordingly. >> >> >> >> -- >> Timo Heister >> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.math.clemson.edu_-7Eheister_&d=DwIGaQ&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=Wl19MSBMb4DZXdORUmp5jA&m=LL9fug0ZE7qJZzKQjUMkIsvL0aLvN-x7mpaYSYowf0A&s=8itYzocifGA6w2VjgGfIUF8ggCVaEbTpKqY9aKKwCfc&e= >> _______________________________________________ >> Aspect-devel mailing list >> Aspect-devel at geodynamics.org >> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.geodynamics.org_cgi-2Dbin_mailman_listinfo_aspect-2Ddevel&d=DwIGaQ&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=Wl19MSBMb4DZXdORUmp5jA&m=LL9fug0ZE7qJZzKQjUMkIsvL0aLvN-x7mpaYSYowf0A&s=GClD7drldCjJ0bq0-jgj8K7TClGgOnpUcEYULdN5RCs&e= >> > > > > _______________________________________________ > Aspect-devel mailing listAspect-devel at geodynamics.orghttp://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel > > > -- > Rene Gassmoellerhttp://www.math.colostate.edu/~gassmoel/ > > > _______________________________________________ > Aspect-devel mailing list > Aspect-devel at geodynamics.org > https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.geodynamics.org_cgi-2Dbin_mailman_listinfo_aspect-2Ddevel&d=DwIGaQ&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=Wl19MSBMb4DZXdORUmp5jA&m=LL9fug0ZE7qJZzKQjUMkIsvL0aLvN-x7mpaYSYowf0A&s=GClD7drldCjJ0bq0-jgj8K7TClGgOnpUcEYULdN5RCs&e= > -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Subject: Digest Footer _______________________________________________ Aspect-devel mailing list Aspect-devel at geodynamics.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.geodynamics.org_cgi-2Dbin_mailman_listinfo_aspect-2Ddevel&d=DwIGaQ&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=Wl19MSBMb4DZXdORUmp5jA&m=LL9fug0ZE7qJZzKQjUMkIsvL0aLvN-x7mpaYSYowf0A&s=GClD7drldCjJ0bq0-jgj8K7TClGgOnpUcEYULdN5RCs&e= ------------------------------ End of Aspect-devel Digest, Vol 71, Issue 5 ******************************************* -------------- next part -------------- An HTML attachment was scrubbed... URL: From rene.gassmoeller at mailbox.org Fri Oct 20 09:24:35 2017 From: rene.gassmoeller at mailbox.org (Rene Gassmoeller) Date: Fri, 20 Oct 2017 10:24:35 -0600 Subject: [aspect-devel] Moving plugins into main ASPECT In-Reply-To: References: <1DA49A49-264A-4CEC-B37F-3DE5A410D5FE@elsi.jp> <731e47d0-4789-3d95-5398-d4134c3ce4f1@gmail.com> <649ab594-fbe0-d315-2876-37a5fcd95762@gmail.com> <1B6322DC-F3DE-4E3F-942C-238093A874F5@elsi.jp> <98310A63-DD20-427B-9D89-9E8AD5A61F34@elsi.jp> Message-ID: <60715cba-d3e0-fdfa-918d-60af4aa99988@mailbox.org> > - about inner_core : the cluster here can’t handle external library, > so we had to add the inner_core.cc to the main ASPECT (which is the > main reason we ended up forking aspect). However, it seems that we did > it quite abruptly… and so the aspect binary we obtain doing that works > OK for inner core, but can’t do any other thing (like testing with box > convection). I guess we should do that differently, but I am not sure > how? How to include inner_core properly into aspect? (splitting > inner_core.cc with a inner_core.h ? any other things?) Hi Marine, let me start with the first problem (Juliane has some answers on your other questions later today), and let me cc the mailing list, because this is actually an instructive question that might help others as well. Your approach is correct, if you are unable to compile shared libraries on your cluster you should move the plugin you need into the main project. In principle every source file you simply move into ASPECT's /source directory and every header file you move into the /include directory is included when compiling ASPECT after rerunning cmake. You do not need to split the declaration and definition into source and header files, it has some practical advantages and is considered better style (that is why we do it with all normal plugins ;-)), but if the plugin in question is in a single .cc file you can keep it in that single file and move it into the /source folder. In your particular case (the inner_core.cc) the plugin contains a material model and a heating model, and an additional assembly term. The material model and heating model should work as expected. The complication arises from the fact that the assembly term is unconditionally added to the assembly whenever this .cc file is included. This is not a problem if it is in a plugin, but if it is in the main project you can not run models that do not use this term anymore. The simplest solution I can see would be to comment/uncomment the following lines of inner_core.cc depending on whether you want to run inner core models or not: ASPECT_REGISTER_SIGNALS_CONNECTOR(signal_connector<2>,        signal_connector<3>) This of course requires recompilation every time you want to activate/deactivate this term. An alternative would be to remove the following lines from the plugin template void signal_connector (aspect::SimulatorSignals &signals) {   signals.set_assemblers.connect (&aspect::set_assemblers_phase_boundary); } ASPECT_REGISTER_SIGNALS_CONNECTOR(signal_connector<2>,                                   signal_connector<3>) and add the following line to the material models (not the heating models) parse_parameters() function: this->get_signals().set_assemblers.connect (&aspect::set_assemblers_phase_boundary); Now the additional assembler term should only be connected if you select this material model. Let me know how that goes, or if you have other questions. Best, Rene From jbnaliboff at ucdavis.edu Fri Oct 20 09:45:16 2017 From: jbnaliboff at ucdavis.edu (John Naliboff) Date: Fri, 20 Oct 2017 09:45:16 -0700 Subject: [aspect-devel] Using seismic tomography as an input In-Reply-To: References: Message-ID: <896fcab6-e76a-4e03-bae8-37115066f886@ucdavis.edu> Hi Paul, Hi Phil, Phil - I used a compositional field to import CRUST1.0 densities into ASPECT via ASCII files. I think this approach (or something very similar) is the only option for handling shallow (lithospheric) density anomalies, as mapping the velocity variations to temperature perturbations gives unrealistically large values due to the compositional origin of the velocity variations. The downside to this approach is that one has to write a material model that specifically handles densities being derived from a compositional field. Perhaps an approach where material models are composited (Jonathan Robey implemented this feature) would work? Cheers, John ************************************************* John Naliboff Assistant Project Scientist, CIG Earth & Planetary Sciences Dept., UC Davis On 10/20/2017 06:52 AM, Bremner,Paul M wrote: > > Hi John, Phil, > > > Something I've had on my back burner is to add functionality to > the S40RTS plug-in (maybe ascii too?) to optionally use the > initial density distribution obtained when mapping the seismic > velocities to temperature. But perhaps there is a different way of > doing this, or maybe the density mapping wasn't used for a reason. > Thoughts? > > > - Paul > > > > ------------------------------------------------------------------------ > *From:* Aspect-devel on behalf > of aspect-devel-request at geodynamics.org > > *Sent:* Friday, October 20, 2017 12:27 AM > *To:* aspect-devel at geodynamics.org > *Subject:* Aspect-devel Digest, Vol 71, Issue 5 > Send Aspect-devel mailing list submissions to >         aspect-devel at geodynamics.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.geodynamics.org_cgi-2Dbin_mailman_listinfo_aspect-2Ddevel&d=DwIGaQ&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=Wl19MSBMb4DZXdORUmp5jA&m=LL9fug0ZE7qJZzKQjUMkIsvL0aLvN-x7mpaYSYowf0A&s=GClD7drldCjJ0bq0-jgj8K7TClGgOnpUcEYULdN5RCs&e= > > or, via email, send a message with subject or body 'help' to >         aspect-devel-request at geodynamics.org > > You can reach the person managing the list at >         aspect-devel-owner at geodynamics.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Aspect-devel digest..." > > > Today's Topics: > >    1. Re: Using seismic tomography as an input (John Naliboff) >    2. Re: Using seismic tomography as an input (Bremner,Paul M) >    3. Re: Dynamic topography (Lev Karatun) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 19 Oct 2017 12:53:26 -0700 > From: John Naliboff > To: aspect-devel at geodynamics.org > Subject: Re: [aspect-devel] Using seismic tomography as an input > Message-ID: <85b6b133-5ac6-36bb-f708-2ae5287c8934 at ucdavis.edu> > Content-Type: text/plain; charset="windows-1252"; Format="flowed" > > Hi Phil, > > It certainly is possible. The plugin for S40RTS maps seismic velocity > variations to temperature, which are provided as the initial condition. > While it make sense to map S40RTS into a spherical coordinate system, it > is straightforward to map a seismic velocity model in cartesian > coordinates. One simply needs to specify how the geographic coordinates > map to a cartesian grid. > > One can also read in the initial temperature field through the ascii > input option (e.g., velocity->temperature are done externally). The user > simply has to take into account the formatting requirements for each > coordinate system (specified in the documentation) when reading in the > ascii data. One can also specify the initial compositional field > structure via ascii text files. I've used this method for reading in > CRUST1.0 in various coordinate systems. So, lots of options! > > If one of your colleagues has specific questions or needs to help > getting started, please have them contact us! > > Cheers, > John > > ************************************************* > John Naliboff > Assistant Project Scientist, CIG > Earth & Planetary Sciences Dept., UC Davis > > On 10/19/2017 12:37 PM, HERON, PHILIP J. wrote: > > > > Hi all, > > > > > > I've had a number of people asking me about using ASPECT with > > available seismic tomography data - to input seismic data and obtain > > density and possibly gravity models. I know this is possible for > > global spherical models (as shown the S20RTS), but is it possible for > > a 3D cartesian seismic input? Or would this require working on a > plug in? > > > > > > Cheers, > > > > > > Phil > > > > > > > > > > > > > > _______________________________________________ > > Aspect-devel mailing list > > Aspect-devel at geodynamics.org > > > https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.geodynamics.org_cgi-2Dbin_mailman_listinfo_aspect-2Ddevel&d=DwIGaQ&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=Wl19MSBMb4DZXdORUmp5jA&m=LL9fug0ZE7qJZzKQjUMkIsvL0aLvN-x7mpaYSYowf0A&s=GClD7drldCjJ0bq0-jgj8K7TClGgOnpUcEYULdN5RCs&e= > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > > > ------------------------------ > > Message: 2 > Date: Thu, 19 Oct 2017 21:04:30 +0000 > From: "Bremner,Paul M" > To: "aspect-devel at geodynamics.org" > Subject: Re: [aspect-devel] Using seismic tomography as an input > Message-ID: > > > Content-Type: text/plain; charset="iso-8859-1" > > Hi Phil, > > > I believe a 3D Cartesian model can be input into the ascii plug-in. > > > I also just want to make sure I understand your purpose correctly, are > you hoping to input seismic tomography models for the express purpose > of obtaining a density and gravity model? Or are you wanting to simply > use the tomography models to feed a density model to ASPECT? > > > I believe that both the S40RTS and ascii plug-ins assign the > temperature field in ASPECT, and not the density. For example, in > S40RTS the velocity perturbation at a particular point is converted to > density perturbation by multiplying a constant scale factor. That > value is then multiplied by 1/alpha to get temperature perturbation, > which is added to a background temperature for that point. > > Cheers, > Paul > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Aspect-devel mailing list > Aspect-devel at geodynamics.org > https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.geodynamics.org_cgi-2Dbin_mailman_listinfo_aspect-2Ddevel&d=DwIGaQ&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=Wl19MSBMb4DZXdORUmp5jA&m=IlyCRz3zvOcycd_IMQiBKL7HsdUkdvb1HQwsaicq2-Q&s=iQC22OjEmDV_vdq0wXaZKucakl7GNkgA7aySC5tDJaE&e= > > ------------------------------ > > End of Aspect-devel Digest, Vol 71, Issue 4 > ******************************************* > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > > > ------------------------------ > > Message: 3 > Date: Thu, 19 Oct 2017 23:41:07 -0400 > From: Lev Karatun > To: "aspect-devel at geodynamics.org" > Subject: Re: [aspect-devel] Dynamic topography > Message-ID: > > Content-Type: text/plain; charset="utf-8" > > Thank you everyone for the responses! > > I kind of realized dynamic topography should be around zero when free > surface in enabled, but in reality in some of my models it was not > (reaching hundreds and even thousands of meters). I assume it means the > errors were high when the surface displacements were calculated? Should I > be worried about it? Is there a way to fight it? I tried decreasing the > free surface solver tolerance, but it didn't help. > > Best regards, > Lev Karatun. > > 2017-10-19 15:23 GMT-04:00 Rene Gassmoeller > : > > > As Ian mentioned, unfortunately there is currently no option to do this. > > > > There is an open issue for this fact: > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_geodynamics&d=DwIGaQ&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=Wl19MSBMb4DZXdORUmp5jA&m=LL9fug0ZE7qJZzKQjUMkIsvL0aLvN-x7mpaYSYowf0A&s=5TaO9E57deZ5NcMMBpIje94EhzplkyR6wWQPaLXtzOE&e= > > > /aspect/issues/1270, and it is on the list of things that 'should be > > done', but never get done, because there are always more important > things > > to do. If anyone wants to go ahead with this issue, we would be grateful > > for it :-). > > > > Best, > > > > Rene > > > > On 10/19/2017 11:18 AM, Ian Rose wrote: > > > > A bit of context: I agree that the naming of the "topography" and > "dynamic > > topography" postprocessors are a bit confusing (the distinction is > > described in the manual, section A.114). They are that way largely for > > historical reasons, as Jacky and I were working on those at roughly the > > same time and did not coordinate naming efforts. But yes, what > Wolfgang and > > Timo say is correct: they are measuring different things. With a free > > surface, you expect the dynamic topgraphy to be near zero, since we are > > enforcing no-stress boundary conditions there! > > > > As to your other question, Lev: the "topography" postprocessor should > > provide an option to output the full topography, rather than just > min/max > > values. It's just that nobody has put in the work to do the parallel I/O > > for it. > > > > Cheers, > > Ian > > > > > > > > On Thu, Oct 19, 2017 at 9:50 AM, Timo Heister > wrote: > > > >> > Or are you saying that the topography you output is due to the moving > >> > boundary? In that case, if the boundary would move in perfect > response > >> to > >> > the fluid stress underneath, then the "dynamic topography" > computed in > >> each > >> > time step would actually be zero, because there are no excess > stresses > >> that > >> > aren't already accommodated by the displaced surface! > >> > >> To add to Wolfgang's reply: > >> This is basically how the free surface implementation works, we > >> compute how much fluid wants to move through the surface and move the > >> surface accordingly. > >> > >> > >> > >> -- > >> Timo Heister > >> > https://urldefense.proofpoint.com/v2/url?u=http-3A__www.math.clemson.edu_-7Eheister_&d=DwIGaQ&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=Wl19MSBMb4DZXdORUmp5jA&m=LL9fug0ZE7qJZzKQjUMkIsvL0aLvN-x7mpaYSYowf0A&s=8itYzocifGA6w2VjgGfIUF8ggCVaEbTpKqY9aKKwCfc&e= > > >> _______________________________________________ > >> Aspect-devel mailing list > >> Aspect-devel at geodynamics.org > >> > https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.geodynamics.org_cgi-2Dbin_mailman_listinfo_aspect-2Ddevel&d=DwIGaQ&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=Wl19MSBMb4DZXdORUmp5jA&m=LL9fug0ZE7qJZzKQjUMkIsvL0aLvN-x7mpaYSYowf0A&s=GClD7drldCjJ0bq0-jgj8K7TClGgOnpUcEYULdN5RCs&e= > > >> > > > > > > > > _______________________________________________ > > Aspect-devel mailing > listAspect-devel at geodynamics.orghttp://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel > > > > > > -- > > Rene Gassmoellerhttp://www.math.colostate.edu/~gassmoel/ > > > > > > _______________________________________________ > > Aspect-devel mailing list > > Aspect-devel at geodynamics.org > > > https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.geodynamics.org_cgi-2Dbin_mailman_listinfo_aspect-2Ddevel&d=DwIGaQ&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=Wl19MSBMb4DZXdORUmp5jA&m=LL9fug0ZE7qJZzKQjUMkIsvL0aLvN-x7mpaYSYowf0A&s=GClD7drldCjJ0bq0-jgj8K7TClGgOnpUcEYULdN5RCs&e= > > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Aspect-devel mailing list > Aspect-devel at geodynamics.org > https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.geodynamics.org_cgi-2Dbin_mailman_listinfo_aspect-2Ddevel&d=DwIGaQ&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=Wl19MSBMb4DZXdORUmp5jA&m=LL9fug0ZE7qJZzKQjUMkIsvL0aLvN-x7mpaYSYowf0A&s=GClD7drldCjJ0bq0-jgj8K7TClGgOnpUcEYULdN5RCs&e= > > > ------------------------------ > > End of Aspect-devel Digest, Vol 71, Issue 5 > ******************************************* > > > _______________________________________________ > Aspect-devel mailing list > Aspect-devel at geodynamics.org > http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel -------------- next part -------------- An HTML attachment was scrubbed... URL: From rene.gassmoeller at mailbox.org Fri Oct 20 10:56:23 2017 From: rene.gassmoeller at mailbox.org (Rene Gassmoeller) Date: Fri, 20 Oct 2017 11:56:23 -0600 Subject: [aspect-devel] Current deal.II development branch broken for ASPECT In-Reply-To: <896fcab6-e76a-4e03-bae8-37115066f886@ucdavis.edu> References: <896fcab6-e76a-4e03-bae8-37115066f886@ucdavis.edu> Message-ID: Hi all, I just wanted to raise awareness for an issue that plagues the interaction of ASPECT with the current development version of deal.II (see https://github.com/geodynamics/aspect/issues/1936). Due to a change in deal.II, a functionality that is required in ASPECT is currently not supported, therefore the current deal.II does not work with any ASPECT version (it will compile flawlessly and then issue errors during runtime). I know some of you lost time trying to update deal.II and figuring out what went wrong (so did I), and I am sorry this situation occurred. The deal.II devs are aware of the situation and working on a fix. As a consequence, currently do *not* update your deal.II development version. Deal.II release 8.5.0/1 and all development versions older or equal than commit |60bfd3170a465002ac1404dc36a5ba9671254b71 |should work without problems. I will let you know when the issue is resolved. Best regards, Rene On 10/20/2017 10:45 AM, John Naliboff wrote: > Hi Paul, Hi Phil, > > Phil - I used a compositional field to import CRUST1.0 densities into > ASPECT via ASCII files. I think this approach (or something very > similar) is the only option for handling shallow (lithospheric) > density anomalies, as mapping the velocity variations to temperature > perturbations gives unrealistically large values due to the > compositional origin of the velocity variations. > > The downside to this approach is that one has to write a material > model that specifically handles densities being derived from a > compositional field. Perhaps an approach where material models are > composited (Jonathan Robey implemented this feature) would work? > > Cheers, > John > > ************************************************* > John Naliboff > Assistant Project Scientist, CIG > Earth & Planetary Sciences Dept., UC Davis > On 10/20/2017 06:52 AM, Bremner,Paul M wrote: >> >> Hi John, Phil, >> >> >> Something I've had on my back burner is to add functionality to >> the S40RTS plug-in (maybe ascii too?) to optionally use the >> initial density distribution obtained when mapping the seismic >> velocities to temperature. But perhaps there is a different way of >> doing this, or maybe the density mapping wasn't used for a reason. >> Thoughts? >> >> >> - Paul >> >> >> >> ------------------------------------------------------------------------ >> *From:* Aspect-devel on behalf >> of aspect-devel-request at geodynamics.org >> >> *Sent:* Friday, October 20, 2017 12:27 AM >> *To:* aspect-devel at geodynamics.org >> *Subject:* Aspect-devel Digest, Vol 71, Issue 5 >> Send Aspect-devel mailing list submissions to >> aspect-devel at geodynamics.org >> >> To subscribe or unsubscribe via the World Wide Web, visit >> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.geodynamics.org_cgi-2Dbin_mailman_listinfo_aspect-2Ddevel&d=DwIGaQ&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=Wl19MSBMb4DZXdORUmp5jA&m=LL9fug0ZE7qJZzKQjUMkIsvL0aLvN-x7mpaYSYowf0A&s=GClD7drldCjJ0bq0-jgj8K7TClGgOnpUcEYULdN5RCs&e= >> >> or, via email, send a message with subject or body 'help' to >> aspect-devel-request at geodynamics.org >> >> You can reach the person managing the list at >> aspect-devel-owner at geodynamics.org >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of Aspect-devel digest..." >> >> >> Today's Topics: >> >>    1. Re: Using seismic tomography as an input (John Naliboff) >>    2. Re: Using seismic tomography as an input (Bremner,Paul M) >>    3. Re: Dynamic topography (Lev Karatun) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Thu, 19 Oct 2017 12:53:26 -0700 >> From: John Naliboff >> To: aspect-devel at geodynamics.org >> Subject: Re: [aspect-devel] Using seismic tomography as an input >> Message-ID: <85b6b133-5ac6-36bb-f708-2ae5287c8934 at ucdavis.edu> >> Content-Type: text/plain; charset="windows-1252"; Format="flowed" >> >> Hi Phil, >> >> It certainly is possible. The plugin for S40RTS maps seismic velocity >> variations to temperature, which are provided as the initial condition. >> While it make sense to map S40RTS into a spherical coordinate system, it >> is straightforward to map a seismic velocity model in cartesian >> coordinates. One simply needs to specify how the geographic coordinates >> map to a cartesian grid. >> >> One can also read in the initial temperature field through the ascii >> input option (e.g., velocity->temperature are done externally). The user >> simply has to take into account the formatting requirements for each >> coordinate system (specified in the documentation) when reading in the >> ascii data. One can also specify the initial compositional field >> structure via ascii text files. I've used this method for reading in >> CRUST1.0 in various coordinate systems. So, lots of options! >> >> If one of your colleagues has specific questions or needs to help >> getting started, please have them contact us! >> >> Cheers, >> John >> >> ************************************************* >> John Naliboff >> Assistant Project Scientist, CIG >> Earth & Planetary Sciences Dept., UC Davis >> >> On 10/19/2017 12:37 PM, HERON, PHILIP J. wrote: >> > >> > Hi all, >> > >> > >> > I've had a number of people asking me about using ASPECT with >> > available seismic tomography data - to input seismic data and obtain >> > density and possibly gravity models. I know this is possible for >> > global spherical models (as shown the S20RTS), but is it possible for >> > a 3D cartesian seismic input? Or would this require working on a >> plug in? >> > >> > >> > Cheers, >> > >> > >> > Phil >> > >> > >> > >> > >> > >> > >> > _______________________________________________ >> > Aspect-devel mailing list >> > Aspect-devel at geodynamics.org >> > >> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.geodynamics.org_cgi-2Dbin_mailman_listinfo_aspect-2Ddevel&d=DwIGaQ&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=Wl19MSBMb4DZXdORUmp5jA&m=LL9fug0ZE7qJZzKQjUMkIsvL0aLvN-x7mpaYSYowf0A&s=GClD7drldCjJ0bq0-jgj8K7TClGgOnpUcEYULdN5RCs&e= >> >> >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: >> > > >> >> ------------------------------ >> >> Message: 2 >> Date: Thu, 19 Oct 2017 21:04:30 +0000 >> From: "Bremner,Paul M" >> To: "aspect-devel at geodynamics.org" >> Subject: Re: [aspect-devel] Using seismic tomography as an input >> Message-ID: >> >> >> Content-Type: text/plain; charset="iso-8859-1" >> >> Hi Phil, >> >> >> I believe a 3D Cartesian model can be input into the ascii plug-in. >> >> >> I also just want to make sure I understand your purpose correctly, >> are you hoping to input seismic tomography models for the express >> purpose of obtaining a density and gravity model? Or are you wanting >> to simply use the tomography models to feed a density model to ASPECT? >> >> >> I believe that both the S40RTS and ascii plug-ins assign the >> temperature field in ASPECT, and not the density. For example, in >> S40RTS the velocity perturbation at a particular point is converted >> to density perturbation by multiplying a constant scale factor. That >> value is then multiplied by 1/alpha to get temperature perturbation, >> which is added to a background temperature for that point. >> >> Cheers, >> Paul >> ------------------------------ >> >> Subject: Digest Footer >> >> _______________________________________________ >> Aspect-devel mailing list >> Aspect-devel at geodynamics.org >> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.geodynamics.org_cgi-2Dbin_mailman_listinfo_aspect-2Ddevel&d=DwIGaQ&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=Wl19MSBMb4DZXdORUmp5jA&m=IlyCRz3zvOcycd_IMQiBKL7HsdUkdvb1HQwsaicq2-Q&s=iQC22OjEmDV_vdq0wXaZKucakl7GNkgA7aySC5tDJaE&e= >> >> ------------------------------ >> >> End of Aspect-devel Digest, Vol 71, Issue 4 >> ******************************************* >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: >> > > >> >> ------------------------------ >> >> Message: 3 >> Date: Thu, 19 Oct 2017 23:41:07 -0400 >> From: Lev Karatun >> To: "aspect-devel at geodynamics.org" >> Subject: Re: [aspect-devel] Dynamic topography >> Message-ID: >> >> Content-Type: text/plain; charset="utf-8" >> >> Thank you everyone for the responses! >> >> I kind of realized dynamic topography should be around zero when free >> surface in enabled, but in reality in some of my models it was not >> (reaching hundreds and even thousands of meters). I assume it means the >> errors were high when the surface displacements were calculated? Should I >> be worried about it? Is there a way to fight it? I tried decreasing the >> free surface solver tolerance, but it didn't help. >> >> Best regards, >> Lev Karatun. >> >> 2017-10-19 15:23 GMT-04:00 Rene Gassmoeller >> : >> >> > As Ian mentioned, unfortunately there is currently no option to do >> this. >> > >> > There is an open issue for this fact: >> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_geodynamics&d=DwIGaQ&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=Wl19MSBMb4DZXdORUmp5jA&m=LL9fug0ZE7qJZzKQjUMkIsvL0aLvN-x7mpaYSYowf0A&s=5TaO9E57deZ5NcMMBpIje94EhzplkyR6wWQPaLXtzOE&e= >> >> > /aspect/issues/1270, and it is on the list of things that 'should be >> > done', but never get done, because there are always more important >> things >> > to do. If anyone wants to go ahead with this issue, we would be >> grateful >> > for it :-). >> > >> > Best, >> > >> > Rene >> > >> > On 10/19/2017 11:18 AM, Ian Rose wrote: >> > >> > A bit of context: I agree that the naming of the "topography" and >> "dynamic >> > topography" postprocessors are a bit confusing (the distinction is >> > described in the manual, section A.114). They are that way largely for >> > historical reasons, as Jacky and I were working on those at roughly the >> > same time and did not coordinate naming efforts. But yes, what >> Wolfgang and >> > Timo say is correct: they are measuring different things. With a free >> > surface, you expect the dynamic topgraphy to be near zero, since we are >> > enforcing no-stress boundary conditions there! >> > >> > As to your other question, Lev: the "topography" postprocessor should >> > provide an option to output the full topography, rather than just >> min/max >> > values. It's just that nobody has put in the work to do the >> parallel I/O >> > for it. >> > >> > Cheers, >> > Ian >> > >> > >> > >> > On Thu, Oct 19, 2017 at 9:50 AM, Timo Heister >> wrote: >> > >> >> > Or are you saying that the topography you output is due to the >> moving >> >> > boundary? In that case, if the boundary would move in perfect >> response >> >> to >> >> > the fluid stress underneath, then the "dynamic topography" >> computed in >> >> each >> >> > time step would actually be zero, because there are no excess >> stresses >> >> that >> >> > aren't already accommodated by the displaced surface! >> >> >> >> To add to Wolfgang's reply: >> >> This is basically how the free surface implementation works, we >> >> compute how much fluid wants to move through the surface and move the >> >> surface accordingly. >> >> >> >> >> >> >> >> -- >> >> Timo Heister >> >> >> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.math.clemson.edu_-7Eheister_&d=DwIGaQ&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=Wl19MSBMb4DZXdORUmp5jA&m=LL9fug0ZE7qJZzKQjUMkIsvL0aLvN-x7mpaYSYowf0A&s=8itYzocifGA6w2VjgGfIUF8ggCVaEbTpKqY9aKKwCfc&e= >> >> >> _______________________________________________ >> >> Aspect-devel mailing list >> >> Aspect-devel at geodynamics.org >> >> >> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.geodynamics.org_cgi-2Dbin_mailman_listinfo_aspect-2Ddevel&d=DwIGaQ&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=Wl19MSBMb4DZXdORUmp5jA&m=LL9fug0ZE7qJZzKQjUMkIsvL0aLvN-x7mpaYSYowf0A&s=GClD7drldCjJ0bq0-jgj8K7TClGgOnpUcEYULdN5RCs&e= >> >> >> >> > >> > >> > >> > _______________________________________________ >> > Aspect-devel mailing >> listAspect-devel at geodynamics.orghttp://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel >> > >> > >> > -- >> > Rene Gassmoellerhttp://www.math.colostate.edu/~gassmoel/ >> > >> > >> > _______________________________________________ >> > Aspect-devel mailing list >> > Aspect-devel at geodynamics.org >> > >> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.geodynamics.org_cgi-2Dbin_mailman_listinfo_aspect-2Ddevel&d=DwIGaQ&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=Wl19MSBMb4DZXdORUmp5jA&m=LL9fug0ZE7qJZzKQjUMkIsvL0aLvN-x7mpaYSYowf0A&s=GClD7drldCjJ0bq0-jgj8K7TClGgOnpUcEYULdN5RCs&e= >> >> > >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: >> > > >> >> ------------------------------ >> >> Subject: Digest Footer >> >> _______________________________________________ >> Aspect-devel mailing list >> Aspect-devel at geodynamics.org >> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.geodynamics.org_cgi-2Dbin_mailman_listinfo_aspect-2Ddevel&d=DwIGaQ&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=Wl19MSBMb4DZXdORUmp5jA&m=LL9fug0ZE7qJZzKQjUMkIsvL0aLvN-x7mpaYSYowf0A&s=GClD7drldCjJ0bq0-jgj8K7TClGgOnpUcEYULdN5RCs&e= >> >> >> ------------------------------ >> >> End of Aspect-devel Digest, Vol 71, Issue 5 >> ******************************************* >> >> >> _______________________________________________ >> Aspect-devel mailing list >> Aspect-devel at geodynamics.org >> http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel > > > > _______________________________________________ > Aspect-devel mailing list > Aspect-devel at geodynamics.org > http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel -- Rene Gassmoeller http://www.math.colostate.edu/~gassmoel/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From jbnaliboff at ucdavis.edu Fri Oct 20 09:53:23 2017 From: jbnaliboff at ucdavis.edu (John Naliboff) Date: Fri, 20 Oct 2017 09:53:23 -0700 Subject: [aspect-devel] Using seismic tomography as an input In-Reply-To: References: Message-ID: <51f3ae2d-40e0-e5a1-c559-7f6d1b295911@ucdavis.edu> Hi Phil, There are currently postprocessors available for computing the geoid and heat flux. Additional postprocessors for gravity are in the works. Working examples - yes, please have your colleague send an email when they have a concrete idea of what they would like to do. If they simply want to map velocity variations into temperature anomalies that are used as an initial condition, this should be fairly straightforward. Cheers, John ************************************************* John Naliboff Assistant Project Scientist, CIG Earth & Planetary Sciences Dept., UC Davis On 10/20/2017 01:37 AM, HERON, PHILIP J. wrote: > > Hi Paul and John, > > > Thanks for the replies! > > > "are you hoping to input seismic tomography models for the express > purpose of obtaining a density and gravity model?" > > > Yes, this is what he is looking to do. Heat flux would be a bonus, too. > > > I've passed on the information and he is going to download Aspect this > afternoon. I think this would be really neat if we can get a working > example up and running from this. I'll keep you posted and I (or more > than likely he) will drop back in with some questions. > > > Thanks again, > > > Phil > > ------------------------------------------------------------------------ > *From:* Aspect-devel on behalf > of Bremner,Paul M > *Sent:* 19 October 2017 22:04:30 > *To:* aspect-devel at geodynamics.org > *Subject:* Re: [aspect-devel] Using seismic tomography as an input > > Hi Phil, > > > I believe a 3D Cartesian model can be input into the ascii plug-in. > > > I also just want to make sure I understand your purpose correctly, are > you hoping to input seismic tomography models for the express purpose > of obtaining a density and gravity model? Or are you wanting to simply > use the tomography models to feed a density model to ASPECT? > > > I believe that both the S40RTS and ascii plug-ins assign the > temperature field in ASPECT, and not the density. For example, in > S40RTS the velocity perturbation at a particular point is converted to > density perturbation by multiplying a constant scale factor. That > value is then multiplied by 1/alpha to get temperature perturbation, > which is added to a background temperature for that point. > > > Cheers, > Paul > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Aspect-devel mailing list > Aspect-devel at geodynamics.org > https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.geodynamics.org_cgi-2Dbin_mailman_listinfo_aspect-2Ddevel&d=DwIGaQ&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=Wl19MSBMb4DZXdORUmp5jA&m=IlyCRz3zvOcycd_IMQiBKL7HsdUkdvb1HQwsaicq2-Q&s=iQC22OjEmDV_vdq0wXaZKucakl7GNkgA7aySC5tDJaE&e= > > > ------------------------------ > > End of Aspect-devel Digest, Vol 71, Issue 4 > ******************************************* > > > _______________________________________________ > Aspect-devel mailing list > Aspect-devel at geodynamics.org > http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel -------------- next part -------------- An HTML attachment was scrubbed... URL: From nuno.m.simao at durham.ac.uk Wed Oct 25 01:50:15 2017 From: nuno.m.simao at durham.ac.uk (=?UTF-8?Q?Nuno_Mendes_Sim=c3=a3o?=) Date: Wed, 25 Oct 2017 09:50:15 +0100 Subject: [aspect-devel] Fwd: Fw: Using seismic tomography as an input In-Reply-To: References: Message-ID: <1277f227-96f4-6925-7aa1-89034853d9b4@durham.ac.uk> Hi Everyone To start a thank you to Phil Heron to introduce me to the exciting world of aspect and to you all for any help. So... I would like to use a Cartesian rectangular box 60*60*13 km (0.5 km steps) oceanic Lithospheric/crustal P-velocity 3D model of a section of an oceanic ridge to calculate > 1st and mainly its gravimetric anomaly, to be compared with ship borne recorded gravimetric anomaly. I understand that the bathymetry is needed to calculate the full gravimetric anomaly, as a big portion of its signal is caused by the interface between the water column and the seafloor. If the use of bathymetry makes things difficult it would still be great to have a tool that only calculates the geopotential anomaly caused by the tomographic Cartesian box defined above. It would be straightforward for me later to subtract the effect of the water column - seafloor from the gravimetric observations to make the comparisons. > and 2nd if possible its Heat flux density > As a note. Normally when I do this in 2d cases I extract the contours that define the velocity ranges that define discrete rheological layers using a seismic velocity-density coefficient for each layer and use the method of Talwani to calculate the geopotential anomalies. Nuno -------- Forwarded Message -------- Subject: Fw: [aspect-devel] Using seismic tomography as an input Date: Fri, 20 Oct 2017 22:36:00 +0100 From: HERON, PHILIP J. To: MENDES-SIMAO, NUNO MIGUEL Philip J. Heron Junior Research Fellow Dept. of Earth Sciences Durham University web: http://philheron.com ------------------------------------------------------------------------ *From:* Aspect-devel on behalf of John Naliboff *Sent:* 20 October 2017 17:53:23 *To:* aspect-devel at geodynamics.org *Subject:* Re: [aspect-devel] Using seismic tomography as an input   Hi Phil, There are currently postprocessors available for computing the geoid and heat flux. Additional postprocessors for gravity are in the works. Working examples - yes, please have your colleague send an email when they have a concrete idea of what they would like to do. If they simply want to map velocity variations into temperature anomalies that are used as an initial condition, this should be fairly straightforward. Cheers, John ************************************************* John Naliboff Assistant Project Scientist, CIG Earth & Planetary Sciences Dept., UC Davis On 10/20/2017 01:37 AM, HERON, PHILIP J. wrote: > > Hi Paul and John, > > > Thanks for the replies! > > > "are you hoping to input seismic tomography models for the express > purpose of obtaining a density and gravity model?" > > > Yes, this is what he is looking to do. Heat flux would be a bonus, too. > > > I've passed on the information and he is going to download Aspect this > afternoon. I think this would be really neat if we can get a working > example up and running from this. I'll keep you posted and I (or more > than likely he) will drop back in with some questions. > > > Thanks again, > > > Phil > > ------------------------------------------------------------------------ > *From:* Aspect-devel on behalf > of Bremner,Paul M > *Sent:* 19 October 2017 22:04:30 > *To:* aspect-devel at geodynamics.org > *Subject:* Re: [aspect-devel] Using seismic tomography as an input >   > > Hi Phil, > > > I believe a 3D Cartesian model can be input into the ascii plug-in. > > > I also just want to make sure I understand your purpose correctly, are > you hoping to input seismic tomography models for the express purpose > of obtaining a density and gravity model? Or are you wanting to simply > use the tomography models to feed a density model to ASPECT? > > > I believe that both the S40RTS and ascii plug-ins assign the > temperature field in ASPECT, and not the density. For example, in > S40RTS the velocity perturbation at a particular point is converted to > density perturbation by multiplying a constant scale factor. That > value is then multiplied by 1/alpha to get temperature perturbation, > which is added to a background temperature for that point. > > > Cheers, > Paul > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Aspect-devel mailing list > Aspect-devel at geodynamics.org > https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.geodynamics.org_cgi-2Dbin_mailman_listinfo_aspect-2Ddevel&d=DwIGaQ&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=Wl19MSBMb4DZXdORUmp5jA&m=IlyCRz3zvOcycd_IMQiBKL7HsdUkdvb1HQwsaicq2-Q&s=iQC22OjEmDV_vdq0wXaZKucakl7GNkgA7aySC5tDJaE&e= > > > ------------------------------ > > End of Aspect-devel Digest, Vol 71, Issue 4 > ******************************************* > > > _______________________________________________ > Aspect-devel mailing list > Aspect-devel at geodynamics.org > http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel -------------- next part -------------- _______________________________________________ Aspect-devel mailing list Aspect-devel at geodynamics.org http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel From jbnaliboff at ucdavis.edu Wed Oct 25 10:49:10 2017 From: jbnaliboff at ucdavis.edu (John Naliboff) Date: Wed, 25 Oct 2017 10:49:10 -0700 Subject: [aspect-devel] Using seismic tomography as an input In-Reply-To: <1277f227-96f4-6925-7aa1-89034853d9b4@durham.ac.uk> References: <1277f227-96f4-6925-7aa1-89034853d9b4@durham.ac.uk> Message-ID: <852589B7-6BB3-4D35-94EF-1902485E4EA4@ucdavis.edu> Hi Nuno, Thanks for the email and specific details on what you would like to do. A few comments below. So the idea is to convert the crustal-scale tomography model (mid-ocean ridge) to a density structure and then input this into Aspect in order to calculate the Geoid, heat flux density and additional gravity anomalies. Certainly feasible and as mentioned earlier ASPECT already has tools to calculate the Geoid and heat flux. You would have to add new tools for calculating additional ‘gravity anomalies’, but it sounds like you already have experience with this type of calculation. A few things to consider: 1. Converting seismic velocity to density: If heat flux is a desired output, then you will be running a thermal-mechanical simulation. In this case, you would need to break the seismic velocity into compositional and thermal contributions. These separate contributions would then serve as the ‘initial conditions’ in Aspect. My recommendation would be to input the initial composition and temperature field through ASCII data files, which you prepare independently. It sounds like you already have a clear idea of how to convert the seismic velocities into a density structure: > I extract the contours that define > the velocity ranges that define discrete rheological layers using a > seismic velocity-density coefficient 2. You mentioned that > a big portion of its signal is caused by the interface between the water column and the seafloor You can include initial topography (bathymetry) on the top boundary (free surface) in ASPECT. An alternative approach is to have a free-slip top boundary (flat), but include a layer for water (low-density and low-viscosity). I’m not sure if either approach is advantageous for your intended purposes. If deeper lithospheric and upper mantle densities anomalies are not included, you may get large isostatic adjustments? > I would like to use a Cartesian rectangular box 60*60*13 km (0.5 km > steps) oceanic Lithospheric/crustal P-velocity 3D 3. Assuming you have a similar grid spacing (0.5 km) in your numerical model, this will give 374400 elements. The exact model size will depend on the type of element you choose and number of compositional fields, but a model of this size will likely need to be run across a few hundred cores. I recommend starting out with a coarser grid (1-2 km) before jumping to higher resolution models. You can also start out by only modeling a small portion of the domain (ex: 10*10*13 km). AMR will also help reduce your total model size, but these are all steps that that should be taken one at a time. In other words, always best to slowly build complexity before jumping straight into large simulations! I hope this helps and others may chime in with more helpful advice as well. Please let us know as additional questions arise! Cheers, John ************************************************* John Naliboff Assistant Project Scientist, CIG Earth & Planetary Sciences Dept., UC Davis > On Oct 25, 2017, at 1:50 AM, Nuno Mendes Simão wrote: > > Hi Everyone > > To start a thank you to Phil Heron to introduce me to the exciting world > of aspect and to you all for any help. > > So... > > I would like to use a Cartesian rectangular box 60*60*13 km (0.5 km > steps) oceanic Lithospheric/crustal P-velocity 3D model of a section of > an oceanic ridge to calculate > >> 1st and mainly > > its gravimetric anomaly, to be compared with ship borne recorded > gravimetric anomaly. > > I understand that the bathymetry is needed to calculate the full > gravimetric anomaly, as a big portion of its signal is caused by the > interface between the water column and the seafloor. If the use of > bathymetry makes things difficult it would still be great to have a tool > that only calculates the geopotential anomaly caused by the tomographic > Cartesian box defined above. It would be straightforward for me later to > subtract the effect of the water column - seafloor from the gravimetric > observations to make the comparisons. > >> and 2nd if possible > its Heat flux density > >> As a note. > > Normally when I do this in 2d cases I extract the contours that define > the velocity ranges that define discrete rheological layers using a > seismic velocity-density coefficient for each layer and use the method > of Talwani to calculate the geopotential anomalies. > > Nuno > > > > > -------- Forwarded Message -------- > Subject: Fw: [aspect-devel] Using seismic tomography as an input > Date: Fri, 20 Oct 2017 22:36:00 +0100 > From: HERON, PHILIP J. > To: MENDES-SIMAO, NUNO MIGUEL > > > > > > Philip J. Heron > Junior Research Fellow > Dept. of Earth Sciences > Durham University > web: http://philheron.com > > ------------------------------------------------------------------------ > *From:* Aspect-devel on behalf of > John Naliboff > *Sent:* 20 October 2017 17:53:23 > *To:* aspect-devel at geodynamics.org > *Subject:* Re: [aspect-devel] Using seismic tomography as an input > > Hi Phil, > > There are currently postprocessors available for computing the geoid and > heat flux. Additional postprocessors for gravity are in the works. > > Working examples - yes, please have your colleague send an email when > they have a concrete idea of what they would like to do. If they simply > want to map velocity variations into temperature anomalies that are used > as an initial condition, this should be fairly straightforward. > > Cheers, > John > > ************************************************* > John Naliboff > Assistant Project Scientist, CIG > Earth & Planetary Sciences Dept., UC Davis > > On 10/20/2017 01:37 AM, HERON, PHILIP J. wrote: >> >> Hi Paul and John, >> >> >> Thanks for the replies! >> >> >> "are you hoping to input seismic tomography models for the express >> purpose of obtaining a density and gravity model?" >> >> >> Yes, this is what he is looking to do. Heat flux would be a bonus, too. >> >> >> I've passed on the information and he is going to download Aspect this >> afternoon. I think this would be really neat if we can get a working >> example up and running from this. I'll keep you posted and I (or more >> than likely he) will drop back in with some questions. >> >> >> Thanks again, >> >> >> Phil >> >> ------------------------------------------------------------------------ >> *From:* Aspect-devel on behalf >> of Bremner,Paul M >> *Sent:* 19 October 2017 22:04:30 >> *To:* aspect-devel at geodynamics.org >> *Subject:* Re: [aspect-devel] Using seismic tomography as an input >> >> >> Hi Phil, >> >> >> I believe a 3D Cartesian model can be input into the ascii plug-in. >> >> >> I also just want to make sure I understand your purpose correctly, are >> you hoping to input seismic tomography models for the express purpose >> of obtaining a density and gravity model? Or are you wanting to simply >> use the tomography models to feed a density model to ASPECT? >> >> >> I believe that both the S40RTS and ascii plug-ins assign the >> temperature field in ASPECT, and not the density. For example, in >> S40RTS the velocity perturbation at a particular point is converted to >> density perturbation by multiplying a constant scale factor. That >> value is then multiplied by 1/alpha to get temperature perturbation, >> which is added to a background temperature for that point. >> >> >> Cheers, >> Paul >> ------------------------------ >> >> Subject: Digest Footer >> >> _______________________________________________ >> Aspect-devel mailing list >> Aspect-devel at geodynamics.org >> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.geodynamics.org_cgi-2Dbin_mailman_listinfo_aspect-2Ddevel&d=DwIGaQ&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=Wl19MSBMb4DZXdORUmp5jA&m=IlyCRz3zvOcycd_IMQiBKL7HsdUkdvb1HQwsaicq2-Q&s=iQC22OjEmDV_vdq0wXaZKucakl7GNkgA7aySC5tDJaE&e= >> >> >> ------------------------------ >> >> End of Aspect-devel Digest, Vol 71, Issue 4 >> ******************************************* >> >> >> _______________________________________________ >> Aspect-devel mailing list >> Aspect-devel at geodynamics.org >> http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel > > _______________________________________________ > Aspect-devel mailing list > Aspect-devel at geodynamics.org > http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel_______________________________________________ > Aspect-devel mailing list > Aspect-devel at geodynamics.org > http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel -------------- next part -------------- An HTML attachment was scrubbed... URL: From rene.gassmoeller at mailbox.org Wed Oct 25 12:44:38 2017 From: rene.gassmoeller at mailbox.org (Rene Gassmoeller) Date: Wed, 25 Oct 2017 13:44:38 -0600 Subject: [aspect-devel] Using seismic tomography as an input In-Reply-To: <852589B7-6BB3-4D35-94EF-1902485E4EA4@ucdavis.edu> References: <1277f227-96f4-6925-7aa1-89034853d9b4@durham.ac.uk> <852589B7-6BB3-4D35-94EF-1902485E4EA4@ucdavis.edu> Message-ID: Hi Nuno, > I would like to use a Cartesian rectangular box 60*60*13 km (0.5 km > steps) oceanic Lithospheric/crustal P-velocity 3D model of a section of > an oceanic ridge to calculate > >> 1st and mainly > > its gravimetric anomaly, to be compared with ship borne recorded > gravimetric anomaly. Unfortunately, this will likely also be the most complicated part of your model. The currently available 'geoid' postprocessor in ASPECT only allows to compute the gravity anomaly (in terms of perturbation of the geoid) for a global spherical model, because it relies on a decomposition of the gravity and topography contributions into spherical harmonics. I am not particularly familiar with gravity fields in cartesian models, have you already thought about how that would work, or are you looking for advice on the topic? Best, Rene On 10/25/2017 11:49 AM, John Naliboff wrote: > Hi Nuno, > > Thanks for the email and specific details on what you would like to > do.  A few comments below. > > So the idea is to convert the crustal-scale tomography model > (mid-ocean ridge) to a density structure and then input this into > Aspect in order to calculate the Geoid, heat flux density and > additional gravity anomalies. Certainly feasible and as mentioned > earlier ASPECT already has tools to calculate the Geoid and heat flux. > You would have to add new tools for calculating additional ‘gravity > anomalies’, but it sounds like you already have experience with this > type of calculation. > > A few things to consider: > > 1. Converting seismic velocity to density: If heat flux is a desired > output, then you will be running a thermal-mechanical simulation. In > this case, you would need to break the seismic velocity into > compositional and thermal contributions. These separate contributions > would then serve as the ‘initial conditions’ in Aspect. My > recommendation would be to input the initial composition and > temperature field through ASCII data files, which you prepare > independently. It sounds like you already have a clear idea of how to > convert the seismic velocities into a density structure: >> I extract the contours that define >> the velocity ranges that define discrete rheological layers using a >> seismic velocity-density coefficient > > 2. You mentioned that >> a big portion of its signal is caused by the interface between the >> water column and the seafloor > You can include initial topography (bathymetry) on the top boundary > (free surface) in ASPECT. An alternative approach is to have a > free-slip top boundary (flat), but include a layer for water > (low-density and low-viscosity). I’m not sure if either approach is > advantageous for your intended purposes. If deeper lithospheric and > upper mantle densities anomalies are not included, you may get large > isostatic adjustments? > >> I would like to use a Cartesian rectangular box 60*60*13 km (0.5 km >> steps) oceanic Lithospheric/crustal P-velocity 3D > > 3. Assuming you have a similar grid spacing (0.5 km) in your numerical > model, this will give 374400 elements. The exact model size will > depend on the type of element you choose and number of compositional > fields, but a model of this size will likely need to be run across a > few hundred cores. > > I recommend starting out with a coarser grid (1-2 km) before jumping > to higher resolution models. You can also start out by only modeling a > small portion of the domain (ex: 10*10*13 km). AMR will also help > reduce your total model size, but these are all steps that that should > be taken one at a time. In other words, always best to slowly build > complexity before jumping straight into large simulations! > > I hope this helps and others may chime in with more helpful advice as > well. Please let us know as additional questions arise! > > Cheers, > John > > > ************************************************* > John Naliboff > Assistant Project Scientist, CIG > Earth & Planetary Sciences Dept., UC Davis > > > > > > >> On Oct 25, 2017, at 1:50 AM, Nuno Mendes Simão >> > wrote: >> >> Hi Everyone >> >> To start a thank you to Phil Heron to introduce me to the exciting world >> of aspect and to you all for any help. >> >> So... >> >> I would like to use a Cartesian rectangular box 60*60*13 km (0.5 km >> steps) oceanic Lithospheric/crustal P-velocity 3D model of a section of >> an oceanic ridge to calculate >> >>> 1st and mainly >> >> its gravimetric anomaly, to be compared with ship borne recorded >> gravimetric anomaly. >> >> I understand that the bathymetry is needed to calculate the full >> gravimetric anomaly, as a big portion of its signal is caused by the >> interface between the water column and the seafloor. If the use of >> bathymetry makes things difficult it would still be great to have a tool >> that only calculates the geopotential anomaly caused by the tomographic >> Cartesian box defined above. It would be straightforward for me later to >> subtract the effect of the water column - seafloor from the gravimetric >> observations to make the comparisons. >> >>> and 2nd if possible >> its Heat flux density >> >>> As a note. >> >> Normally when I do this in 2d cases I extract the contours that define >> the velocity ranges that define discrete rheological layers using a >> seismic velocity-density coefficient for each layer and use the method >> of Talwani to calculate the geopotential anomalies. >> >> Nuno >> >> >> >> >> -------- Forwarded Message -------- >> Subject: Fw: [aspect-devel] Using seismic tomography as an input >> Date: Fri, 20 Oct 2017 22:36:00 +0100 >> From: HERON, PHILIP J. > > >> To: MENDES-SIMAO, NUNO MIGUEL > > >> >> >> >> >> >> Philip J. Heron >> Junior Research Fellow >> Dept. of Earth Sciences >> Durham University >> web: http://philheron.com >> >> ------------------------------------------------------------------------ >> *From:* Aspect-devel > > on behalf of >> John Naliboff > >> *Sent:* 20 October 2017 17:53:23 >> *To:* aspect-devel at geodynamics.org >> *Subject:* Re: [aspect-devel] Using seismic tomography as an input >> >> Hi Phil, >> >> There are currently postprocessors available for computing the geoid and >> heat flux. Additional postprocessors for gravity are in the works. >> >> Working examples - yes, please have your colleague send an email when >> they have a concrete idea of what they would like to do. If they simply >> want to map velocity variations into temperature anomalies that are used >> as an initial condition, this should be fairly straightforward. >> >> Cheers, >> John >> >> ************************************************* >> John Naliboff >> Assistant Project Scientist, CIG >> Earth & Planetary Sciences Dept., UC Davis >> >> On 10/20/2017 01:37 AM, HERON, PHILIP J. wrote: >>> >>> Hi Paul and John, >>> >>> >>> Thanks for the replies! >>> >>> >>> "are you hoping to input seismic tomography models for the express >>> purpose of obtaining a density and gravity model?" >>> >>> >>> Yes, this is what he is looking to do. Heat flux would be a bonus, too. >>> >>> >>> I've passed on the information and he is going to download Aspect this >>> afternoon. I think this would be really neat if we can get a working >>> example up and running from this. I'll keep you posted and I (or more >>> than likely he) will drop back in with some questions. >>> >>> >>> Thanks again, >>> >>> >>> Phil >>> >>> ------------------------------------------------------------------------ >>> *From:* Aspect-devel >> > on behalf >>> of Bremner,Paul M > >>> *Sent:* 19 October 2017 22:04:30 >>> *To:* aspect-devel at geodynamics.org >>> *Subject:* Re: [aspect-devel] Using seismic tomography as an input >>> >>> >>> Hi Phil, >>> >>> >>> I believe a 3D Cartesian model can be input into the ascii plug-in. >>> >>> >>> I also just want to make sure I understand your purpose correctly, are >>> you hoping to input seismic tomography models for the express purpose >>> of obtaining a density and gravity model? Or are you wanting to simply >>> use the tomography models to feed a density model to ASPECT? >>> >>> >>> I believe that both the S40RTS and ascii plug-ins assign the >>> temperature field in ASPECT, and not the density. For example, in >>> S40RTS the velocity perturbation at a particular point is converted to >>> density perturbation by multiplying a constant scale factor. That >>> value is then multiplied by 1/alpha to get temperature perturbation, >>> which is added to a background temperature for that point. >>> >>> >>> Cheers, >>> Paul >>> ------------------------------ >>> >>> Subject: Digest Footer >>> >>> _______________________________________________ >>> Aspect-devel mailing list >>> Aspect-devel at geodynamics.org >>> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.geodynamics.org_cgi-2Dbin_mailman_listinfo_aspect-2Ddevel&d=DwIGaQ&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=Wl19MSBMb4DZXdORUmp5jA&m=IlyCRz3zvOcycd_IMQiBKL7HsdUkdvb1HQwsaicq2-Q&s=iQC22OjEmDV_vdq0wXaZKucakl7GNkgA7aySC5tDJaE&e= >>> >>> >>> ------------------------------ >>> >>> End of Aspect-devel Digest, Vol 71, Issue 4 >>> ******************************************* >>> >>> >>> _______________________________________________ >>> Aspect-devel mailing list >>> Aspect-devel at geodynamics.org >>> http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel >> >> _______________________________________________ >> Aspect-devel mailing list >> Aspect-devel at geodynamics.org >> http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel_______________________________________________ >> Aspect-devel mailing list >> Aspect-devel at geodynamics.org >> http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel > > > > _______________________________________________ > Aspect-devel mailing list > Aspect-devel at geodynamics.org > http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel -- Rene Gassmoeller http://www.math.colostate.edu/~gassmoel/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From eleonora.ficini at uniroma1.it Wed Oct 25 06:41:46 2017 From: eleonora.ficini at uniroma1.it (Eleonora Ficini) Date: Wed, 25 Oct 2017 15:41:46 +0200 Subject: [aspect-devel] Plate motion reconstrucion - Layered rheology Message-ID: Hello everyone, I am a PhD student, I recently started to use ASPECT and I have two different questions: 1) I would like to know if someone tried to include plate motion reconstruction (from GPlates) into ASPECT. If yes, what kind of files does ASPECT need? It seems that the manual doesn't mention the correct way to built the velocity/time file. 2) In a global spherical model, how is the layered rheological structure (especially regarding a 100 km thick lithosphere)? Thank you in advance for your time and attention. All the best, Eleonora -------------- next part -------------- An HTML attachment was scrubbed... URL: From maxrudolph at ucdavis.edu Wed Oct 25 14:20:55 2017 From: maxrudolph at ucdavis.edu (Maxwell Rudolph) Date: Wed, 25 Oct 2017 14:20:55 -0700 Subject: [aspect-devel] Plate motion reconstrucion - Layered rheology In-Reply-To: References: Message-ID: Eleonora, There is a 'depth dependent' material model that allows you to prescribe a depth-dependent viscosity prefactor to any of the other material models. Max On Wed, Oct 25, 2017 at 6:41 AM, Eleonora Ficini < eleonora.ficini at uniroma1.it> wrote: > Hello everyone, > I am a PhD student, I recently started to use ASPECT and I have two > different questions: > > 1) I would like to know if someone tried to include plate motion > reconstruction (from GPlates) into ASPECT. If yes, what kind of files does > ASPECT need? It seems that the manual doesn't mention the correct way to > built the velocity/time file. > > 2) In a global spherical model, how is the layered rheological structure > (especially regarding a 100 km thick lithosphere)? > > Thank you in advance for your time and attention. > > All the best, > Eleonora > > > _______________________________________________ > Aspect-devel mailing list > Aspect-devel at geodynamics.org > http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: From A.C.Glerum at uu.nl Wed Oct 25 16:33:07 2017 From: A.C.Glerum at uu.nl (Glerum, A.C. (Anne)) Date: Wed, 25 Oct 2017 23:33:07 +0000 Subject: [aspect-devel] Plate motion reconstrucion - Layered rheology In-Reply-To: References: Message-ID: Hi Eleonora, GPlates files can be used as boundary conditions in ASPECT, see for example Heister et al. 2017 GJI. There is a section in the manual that describes how to create the GPlates velocity files: Section 5.3.4 Using reconstructed surface velocities by GPlates What I did recently to create a file for present day velocities was: 1. (1) Load the Reconstruction Tree 2. (2) Load the Dynamic Polygons 3. (3) Generate a grid for the velocity output with Features → Generate Velocity Domain Points 4. (4) This will show velocity vectors for the grid points. Export through Reconstruction → Export I hope that gets you started, Anne On 26 Oct 2017, at 08:20, Maxwell Rudolph > wrote: Eleonora, There is a 'depth dependent' material model that allows you to prescribe a depth-dependent viscosity prefactor to any of the other material models. Max On Wed, Oct 25, 2017 at 6:41 AM, Eleonora Ficini > wrote: Hello everyone, I am a PhD student, I recently started to use ASPECT and I have two different questions: 1) I would like to know if someone tried to include plate motion reconstruction (from GPlates) into ASPECT. If yes, what kind of files does ASPECT need? It seems that the manual doesn't mention the correct way to built the velocity/time file. 2) In a global spherical model, how is the layered rheological structure (especially regarding a 100 km thick lithosphere)? Thank you in advance for your time and attention. All the best, Eleonora _______________________________________________ Aspect-devel mailing list Aspect-devel at geodynamics.org http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel _______________________________________________ Aspect-devel mailing list Aspect-devel at geodynamics.org http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel -------------- next part -------------- An HTML attachment was scrubbed... URL: From rene.gassmoeller at mailbox.org Thu Oct 26 09:58:54 2017 From: rene.gassmoeller at mailbox.org (Rene Gassmoeller) Date: Thu, 26 Oct 2017 10:58:54 -0600 Subject: [aspect-devel] Plate motion reconstrucion - Layered rheology In-Reply-To: References: Message-ID: <4f51844b-6959-7098-df33-99722b105448@mailbox.org> Hi Eleonora, you stated that > It seems that the manual doesn't mention the correct way to built the > velocity/time file. Could you elaborate on that? What is the error message that you see if you follow the instructions that Anne send? If this continues to fail that might mean GPlates has again changed its data format (they did that once in the past, and we currently support both formats). If Anne's suggestions do not help, could you send me which version of ASPECT and GPlates you are using (and ideally also the plate reconstruction you used if that is possible, though better send that in a private email off the mailing list)? Then I can try to reproduce the issue and look for a fix. Best, Rene On 10/25/2017 05:33 PM, Glerum, A.C. (Anne) wrote: > Hi Eleonora, > > GPlates files can be used as boundary conditions in ASPECT, see for > example Heister et al. 2017 GJI. > > There is a section in the manual that describes how to create the > GPlates velocity files: > Section 5.3.4 Using reconstructed surface velocities by GPlates > >  What I did recently to create a file for present day velocities was: > > 1. > > (1)  Load the Reconstruction Tree > > 2. > > (2)  Load the Dynamic Polygons > > 3. > > (3)  Generate a grid for the velocity output with Features → > Generate Velocity Domain Points > > 4. > > (4)  This will show velocity vectors for the grid points. Export > through Reconstruction → Export > > I hope that gets you started, > Anne > > > >> On 26 Oct 2017, at 08:20, Maxwell Rudolph > > wrote: >> >> Eleonora, >> There is a 'depth dependent' material model that allows you to >> prescribe a depth-dependent viscosity prefactor to any of the other >> material models. >> >> Max >> >> On Wed, Oct 25, 2017 at 6:41 AM, Eleonora Ficini >> > wrote: >> >> Hello everyone, >> I am a PhD student, I recently started to use ASPECT and I have >> two different questions: >> >> 1) I would like to know if someone tried to include plate motion >> reconstruction (from GPlates) into ASPECT. If yes, what kind of >> files does ASPECT need? It seems that the manual doesn't mention >> the correct way to built the velocity/time file. >> >> 2) In a global spherical model, how is the layered rheological >> structure (especially regarding a 100 km thick lithosphere)? >> >> Thank you in advance for your time and attention. >> >> All the best, >> Eleonora >> >> >> _______________________________________________ >> Aspect-devel mailing list >> Aspect-devel at geodynamics.org >> http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel >> >> >> >> _______________________________________________ >> Aspect-devel mailing list >> Aspect-devel at geodynamics.org >> http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel > > > > _______________________________________________ > Aspect-devel mailing list > Aspect-devel at geodynamics.org > http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel -- Rene Gassmoeller http://www.math.colostate.edu/~gassmoel/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From eleonora.ficini at uniroma1.it Mon Oct 30 02:37:49 2017 From: eleonora.ficini at uniroma1.it (Eleonora Ficini) Date: Mon, 30 Oct 2017 10:37:49 +0100 Subject: [aspect-devel] Aspect-devel Digest, Vol 71, Issue 12 - Plate motion reconstrucion - Layered rheology - Message-ID: Dear all, thank you for your answers and suggestions. What I wanted to say in the previews mail (sorry if I didn't explain it in a correct way, it probably sounded very rude!) was just that I had a number of error messages in learning the first steps of how include GPlates reconstruction in the ASPECT code: When I try to run the GPlates cookbook example what I get is: * Loading GPlates data boundary file /home/ubuntu/aspect/data/velocity-boundary-conditions/gplates/current_day.gpml.* * Loading new velocity file did not succeed.* * Assuming constant boundary conditions for rest of model run.* Does this mean that ASPECT use the current_day velocities for the entire simulation? Or there's an error occuring when loading the velocity file? I tried then to look for the velocity file (to see how it was built) but I wasn't able to find the source file, neither from the ASPECT link or from the websites mentioned in the manual (in particular, the "Global reconstructions with continuously closing plates from 140 Ma to the present"). The error I got was: *404 Not Found The requested URL /~gurnis/GPlates/gplates.html was not found on this server.* Lastly, with the manual instructions (that also Anne suggested), I tried to build a new velocity file by myself using Seton et al., 2012 reconstruction (that comes with GPlates software 1.5.0) but what I got was: *An error occurred while saving the file 'lat_lon_velocity_domain_9_18.gpml': * *ErrorOpeningFileForWritingException: Error opening file 'lat_lon_velocity_domain_9_18.gpml' for writing* *Call stack trace:* *(/Users/jcannon/gplates/builds/1.5/src/file-io/GpmlOutputVisitor.cc, 551)* I am sorry if any of the mistakes I am making is basic, but I just started to deal with the code. Thank you in advance. All the best, Eleonora 2017-10-26 18:54 GMT+02:00 : > Send Aspect-devel mailing list submissions to > aspect-devel at geodynamics.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel > or, via email, send a message with subject or body 'help' to > aspect-devel-request at geodynamics.org > > You can reach the person managing the list at > aspect-devel-owner at geodynamics.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Aspect-devel digest..." > > > Today's Topics: > > 1. Plate motion reconstrucion - Layered rheology (Eleonora Ficini) > 2. Re: Plate motion reconstrucion - Layered rheology > (Maxwell Rudolph) > 3. Re: Plate motion reconstrucion - Layered rheology > (Glerum, A.C. (Anne)) > 4. Re: Plate motion reconstrucion - Layered rheology > (Rene Gassmoeller) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 25 Oct 2017 15:41:46 +0200 > From: Eleonora Ficini > To: aspect-devel at geodynamics.org > Subject: [aspect-devel] Plate motion reconstrucion - Layered rheology > Message-ID: > eGuHUxAHqw at mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hello everyone, > I am a PhD student, I recently started to use ASPECT and I have two > different questions: > > 1) I would like to know if someone tried to include plate motion > reconstruction (from GPlates) into ASPECT. If yes, what kind of files does > ASPECT need? It seems that the manual doesn't mention the correct way to > built the velocity/time file. > > 2) In a global spherical model, how is the layered rheological structure > (especially regarding a 100 km thick lithosphere)? > > Thank you in advance for your time and attention. > > All the best, > Eleonora > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: attachments/20171025/43f26a72/attachment-0001.html> > > ------------------------------ > > Message: 2 > Date: Wed, 25 Oct 2017 14:20:55 -0700 > From: Maxwell Rudolph > To: aspect-devel at geodynamics.org > Subject: Re: [aspect-devel] Plate motion reconstrucion - Layered > rheology > Message-ID: > gmail.com> > Content-Type: text/plain; charset="utf-8" > > Eleonora, > There is a 'depth dependent' material model that allows you to prescribe a > depth-dependent viscosity prefactor to any of the other material models. > > Max > > On Wed, Oct 25, 2017 at 6:41 AM, Eleonora Ficini < > eleonora.ficini at uniroma1.it> wrote: > > > Hello everyone, > > I am a PhD student, I recently started to use ASPECT and I have two > > different questions: > > > > 1) I would like to know if someone tried to include plate motion > > reconstruction (from GPlates) into ASPECT. If yes, what kind of files > does > > ASPECT need? It seems that the manual doesn't mention the correct way to > > built the velocity/time file. > > > > 2) In a global spherical model, how is the layered rheological structure > > (especially regarding a 100 km thick lithosphere)? > > > > Thank you in advance for your time and attention. > > > > All the best, > > Eleonora > > > > > > _______________________________________________ > > Aspect-devel mailing list > > Aspect-devel at geodynamics.org > > http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: attachments/20171025/7507efa7/attachment-0001.html> > > ------------------------------ > > Message: 3 > Date: Wed, 25 Oct 2017 23:33:07 +0000 > From: "Glerum, A.C. (Anne)" > To: "aspect-devel at geodynamics.org" > Subject: Re: [aspect-devel] Plate motion reconstrucion - Layered > rheology > Message-ID: > Content-Type: text/plain; charset="utf-8" > > Hi Eleonora, > > GPlates files can be used as boundary conditions in ASPECT, see for > example Heister et al. 2017 GJI. > > There is a section in the manual that describes how to create the GPlates > velocity files: > Section 5.3.4 Using reconstructed surface velocities by GPlates > > What I did recently to create a file for present day velocities was: > > 1. (1) Load the Reconstruction Tree > > 2. (2) Load the Dynamic Polygons > > 3. (3) Generate a grid for the velocity output with Features → > Generate Velocity Domain Points > > 4. (4) This will show velocity vectors for the grid points. Export > through Reconstruction → Export > > I hope that gets you started, > Anne > > > > On 26 Oct 2017, at 08:20, Maxwell Rudolph maxrudolph at ucdavis.edu>> wrote: > > Eleonora, > There is a 'depth dependent' material model that allows you to prescribe a > depth-dependent viscosity prefactor to any of the other material models. > > Max > > On Wed, Oct 25, 2017 at 6:41 AM, Eleonora Ficini < > eleonora.ficini at uniroma1.it> wrote: > Hello everyone, > I am a PhD student, I recently started to use ASPECT and I have two > different questions: > > 1) I would like to know if someone tried to include plate motion > reconstruction (from GPlates) into ASPECT. If yes, what kind of files does > ASPECT need? It seems that the manual doesn't mention the correct way to > built the velocity/time file. > > 2) In a global spherical model, how is the layered rheological structure > (especially regarding a 100 km thick lithosphere)? > > Thank you in advance for your time and attention. > > All the best, > Eleonora > > > _______________________________________________ > Aspect-devel mailing list > Aspect-devel at geodynamics.org > http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel > > _______________________________________________ > Aspect-devel mailing list > Aspect-devel at geodynamics.org > http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: attachments/20171025/bf6742ba/attachment-0001.html> > > ------------------------------ > > Message: 4 > Date: Thu, 26 Oct 2017 10:58:54 -0600 > From: Rene Gassmoeller > To: aspect-devel at geodynamics.org > Subject: Re: [aspect-devel] Plate motion reconstrucion - Layered > rheology > Message-ID: <4f51844b-6959-7098-df33-99722b105448 at mailbox.org> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > Hi Eleonora, > > you stated that > > > It seems that the manual doesn't mention the correct way to built the > > velocity/time file. > > Could you elaborate on that? What is the error message that you see if > you follow the instructions that Anne send? > > If this continues to fail that might mean GPlates has again changed its > data format (they did that once in the past, and we currently support > both formats). If Anne's suggestions do not help, could you send me > which version of ASPECT and GPlates you are using (and ideally also the > plate reconstruction you used if that is possible, though better send > that in a private email off the mailing list)? Then I can try to > reproduce the issue and look for a fix. > > Best, > > Rene > > > > On 10/25/2017 05:33 PM, Glerum, A.C. (Anne) wrote: > > Hi Eleonora, > > > > GPlates files can be used as boundary conditions in ASPECT, see for > > example Heister et al. 2017 GJI. > > > > There is a section in the manual that describes how to create the > > GPlates velocity files: > > Section 5.3.4 Using reconstructed surface velocities by GPlates > > > > What I did recently to create a file for present day velocities was: > > > > 1. > > > > (1) Load the Reconstruction Tree > > > > 2. > > > > (2) Load the Dynamic Polygons > > > > 3. > > > > (3) Generate a grid for the velocity output with Features → > > Generate Velocity Domain Points > > > > 4. > > > > (4) This will show velocity vectors for the grid points. Export > > through Reconstruction → Export > > > > I hope that gets you started, > > Anne > > > > > > > >> On 26 Oct 2017, at 08:20, Maxwell Rudolph >> > wrote: > >> > >> Eleonora, > >> There is a 'depth dependent' material model that allows you to > >> prescribe a depth-dependent viscosity prefactor to any of the other > >> material models. > >> > >> Max > >> > >> On Wed, Oct 25, 2017 at 6:41 AM, Eleonora Ficini > >> > > wrote: > >> > >> Hello everyone, > >> I am a PhD student, I recently started to use ASPECT and I have > >> two different questions: > >> > >> 1) I would like to know if someone tried to include plate motion > >> reconstruction (from GPlates) into ASPECT. If yes, what kind of > >> files does ASPECT need? It seems that the manual doesn't mention > >> the correct way to built the velocity/time file. > >> > >> 2) In a global spherical model, how is the layered rheological > >> structure (especially regarding a 100 km thick lithosphere)? > >> > >> Thank you in advance for your time and attention. > >> > >> All the best, > >> Eleonora > >> > >> > >> _______________________________________________ > >> Aspect-devel mailing list > >> Aspect-devel at geodynamics.org > >> http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel > >> > > >> > >> > >> _______________________________________________ > >> Aspect-devel mailing list > >> Aspect-devel at geodynamics.org > >> http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel > > > > > > > > _______________________________________________ > > Aspect-devel mailing list > > Aspect-devel at geodynamics.org > > http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel > > -- > Rene Gassmoeller > http://www.math.colostate.edu/~gassmoel/ > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: attachments/20171026/21377303/attachment.html> > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Aspect-devel mailing list > Aspect-devel at geodynamics.org > http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel > > ------------------------------ > > End of Aspect-devel Digest, Vol 71, Issue 12 > ******************************************** > -- Eleonora Ficini, PhD student Department of Earth Sciences Sapienza University of Rome P.le A. Moro, 5 - 00185, Rome, Italy -------------- next part -------------- An HTML attachment was scrubbed... URL: From rene.gassmoeller at mailbox.org Mon Oct 30 15:48:58 2017 From: rene.gassmoeller at mailbox.org (Rene Gassmoeller) Date: Mon, 30 Oct 2017 16:48:58 -0600 Subject: [aspect-devel] Aspect-devel Digest, Vol 71, Issue 12 - Plate motion reconstrucion - Layered rheology - In-Reply-To: References: Message-ID: <251df413-0a47-db0d-681f-0d4ad034a1d0@mailbox.org> Hi Eleonora, On 10/30/2017 03:37 AM, Eleonora Ficini wrote: > Dear all, > thank you for your answers and suggestions. > What I wanted to say in the previews mail (sorry if I didn't explain > it in a correct way, it probably sounded very rude!) was just that I > had a number of error messages in learning the first steps of how > include GPlates reconstruction in the ASPECT code: > Do not worry, we all started at some point, questions are normal :-) > When I try to run the GPlates cookbook example what I get is: > > / Loading GPlates data boundary file > /home/ubuntu/aspect/data/velocity-boundary-conditions/gplates/current_day.gpml./ > / > / > /   Loading new velocity file did not succeed./ > /   Assuming constant boundary conditions for rest of model run./ > > Does this mean that ASPECT use the current_day velocities for the > entire simulation? Or there's an error occuring when loading the > velocity file? > This message means ASPECT loaded a single file, and noticed the file is not part of a series of data files. Thus it will use this single file for the whole computation. This is not an error in itself. The example input file simply prescribes to use the same velocity file for the whole simulation time. I admit that the warning message could be better formulated. If you want to use time-dependent velocities, you will have to create a dataset in GPlates and use that one, because we do not include such large datasets inside of ASPECT (the process for this is described in the "Time-dependent boundary conditions" paragraph of the GPlates section in the manual). > I tried then to look for the velocity file (to see how it was built) > but I wasn't able to find the source file, neither from the ASPECT > link or from the websites mentioned in the manual (in particular, the > "Global reconstructions with continuously closing plates from 140 Ma > to the present"). The error I got was: > > /404 Not Found The requested URL /~gurnis/GPlates/gplates.html was not > found on this server./ Thanks for this hint, apparently the website has moved. I have opened an issue here: https://github.com/geodynamics/aspect/issues/1979. If we find a solution it will be posted there. > / > / > Lastly, with the manual instructions (that also Anne suggested), I > tried to build a new velocity file by myself using Seton et al., 2012 > reconstruction (that comes with GPlates software 1.5.0)  but what I > got was: > > /An error occurred while saving the file > 'lat_lon_velocity_domain_9_18.gpml': / > > /ErrorOpeningFileForWritingException: Error opening file > 'lat_lon_velocity_domain_9_18.gpml' for writing/ > > /Call stack trace:/ > > /(/Users/jcannon/gplates/builds/1.5/src/file-io/GpmlOutputVisitor.cc, > 551)/ > Hmm, this looks like a problem inside of GPlates. The Seton 2012 dataset should be fine to use (I used that before). Which version of Gplates did you use? And it seems GPlates could not write the file to your disk, are you sure you tried to save it in a location you have write-access to? > / > / > > I am sorry if any of the mistakes I am making is basic, but I just > started to deal with the code. > > Dont worry, some of your points are genuine problems, and others are normal questions, that is what this mailing list is for. Best, Rene > Thank you in advance. > > > All the best, > > Eleonora > > > 2017-10-26 18:54 GMT+02:00 >: > > Send Aspect-devel mailing list submissions to > aspect-devel at geodynamics.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel > > or, via email, send a message with subject or body 'help' to > aspect-devel-request at geodynamics.org > > > You can reach the person managing the list at > aspect-devel-owner at geodynamics.org > > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Aspect-devel digest..." > > > Today's Topics: > >    1. Plate motion reconstrucion - Layered rheology (Eleonora Ficini) >    2. Re: Plate motion reconstrucion - Layered rheology >       (Maxwell Rudolph) >    3. Re: Plate motion reconstrucion - Layered rheology >       (Glerum, A.C. (Anne)) >    4. Re: Plate motion reconstrucion - Layered rheology >       (Rene Gassmoeller) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 25 Oct 2017 15:41:46 +0200 > From: Eleonora Ficini > > To: aspect-devel at geodynamics.org > Subject: [aspect-devel] Plate motion reconstrucion - Layered rheology > Message-ID: >         > > > Content-Type: text/plain; charset="utf-8" > > Hello everyone, > I am a PhD student, I recently started to use ASPECT and I have two > different questions: > > 1) I would like to know if someone tried to include plate motion > reconstruction (from GPlates) into ASPECT. If yes, what kind of > files does > ASPECT need? It seems that the manual doesn't mention the correct > way to > built the velocity/time file. > > 2) In a global spherical model, how is the layered rheological > structure > (especially regarding a 100 km thick lithosphere)? > > Thank you in advance for your time and attention. > > All the best, > Eleonora > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > > > ------------------------------ > > Message: 2 > Date: Wed, 25 Oct 2017 14:20:55 -0700 > From: Maxwell Rudolph > > To: aspect-devel at geodynamics.org > Subject: Re: [aspect-devel] Plate motion reconstrucion - Layered >         rheology > Message-ID: >         > > > Content-Type: text/plain; charset="utf-8" > > Eleonora, > There is a 'depth dependent' material model that allows you to > prescribe a > depth-dependent viscosity prefactor to any of the other material > models. > > Max > > On Wed, Oct 25, 2017 at 6:41 AM, Eleonora Ficini < > eleonora.ficini at uniroma1.it > > wrote: > > > Hello everyone, > > I am a PhD student, I recently started to use ASPECT and I have two > > different questions: > > > > 1) I would like to know if someone tried to include plate motion > > reconstruction (from GPlates) into ASPECT. If yes, what kind of > files does > > ASPECT need? It seems that the manual doesn't mention the > correct way to > > built the velocity/time file. > > > > 2) In a global spherical model, how is the layered rheological > structure > > (especially regarding a 100 km thick lithosphere)? > > > > Thank you in advance for your time and attention. > > > > All the best, > > Eleonora > > > > > > _______________________________________________ > > Aspect-devel mailing list > > Aspect-devel at geodynamics.org > > > http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel > > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > > > ------------------------------ > > Message: 3 > Date: Wed, 25 Oct 2017 23:33:07 +0000 > From: "Glerum, A.C. (Anne)" > > To: "aspect-devel at geodynamics.org > " > > > Subject: Re: [aspect-devel] Plate motion reconstrucion - Layered >         rheology > Message-ID: > > Content-Type: text/plain; charset="utf-8" > > Hi Eleonora, > > GPlates files can be used as boundary conditions in ASPECT, see > for example Heister et al. 2017 GJI. > > There is a section in the manual that describes how to create the > GPlates velocity files: > Section 5.3.4 Using reconstructed surface velocities by GPlates > >  What I did recently to create a file for present day velocities was: > >   1.  (1)  Load the Reconstruction Tree > >   2.  (2)  Load the Dynamic Polygons > >   3.  (3)  Generate a grid for the velocity output with Features → > Generate Velocity Domain Points > >   4.  (4)  This will show velocity vectors for the grid points. > Export through Reconstruction → Export > > I hope that gets you started, > Anne > > > > On 26 Oct 2017, at 08:20, Maxwell Rudolph >> wrote: > > Eleonora, > There is a 'depth dependent' material model that allows you to > prescribe a depth-dependent viscosity prefactor to any of the > other material models. > > Max > > On Wed, Oct 25, 2017 at 6:41 AM, Eleonora Ficini > >> wrote: > Hello everyone, > I am a PhD student, I recently started to use ASPECT and I have > two different questions: > > 1) I would like to know if someone tried to include plate motion > reconstruction (from GPlates) into ASPECT. If yes, what kind of > files does ASPECT need? It seems that the manual doesn't mention > the correct way to built the velocity/time file. > > 2) In a global spherical model, how is the layered rheological > structure (especially regarding a 100 km thick lithosphere)? > > Thank you in advance for your time and attention. > > All the best, > Eleonora > > > _______________________________________________ > Aspect-devel mailing list > Aspect-devel at geodynamics.org > > > http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel > > > _______________________________________________ > Aspect-devel mailing list > Aspect-devel at geodynamics.org > > > http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > > > ------------------------------ > > Message: 4 > Date: Thu, 26 Oct 2017 10:58:54 -0600 > From: Rene Gassmoeller > > To: aspect-devel at geodynamics.org > Subject: Re: [aspect-devel] Plate motion reconstrucion - Layered >         rheology > Message-ID: <4f51844b-6959-7098-df33-99722b105448 at mailbox.org > > > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > Hi Eleonora, > > you stated that > > > It seems that the manual doesn't mention the correct way to > built the > > velocity/time file. > > Could you elaborate on that? What is the error message that you see if > you follow the instructions that Anne send? > > If this continues to fail that might mean GPlates has again > changed its > data format (they did that once in the past, and we currently support > both formats). If Anne's suggestions do not help, could you send me > which version of ASPECT and GPlates you are using (and ideally > also the > plate reconstruction you used if that is possible, though better send > that in a private email off the mailing list)? Then I can try to > reproduce the issue and look for a fix. > > Best, > > Rene > > > > On 10/25/2017 05:33 PM, Glerum, A.C. (Anne) wrote: > > Hi Eleonora, > > > > GPlates files can be used as boundary conditions in ASPECT, see for > > example Heister et al. 2017 GJI. > > > > There is a section in the manual that describes how to create the > > GPlates velocity files: > > Section 5.3.4 Using reconstructed surface velocities by GPlates > > > >  What I did recently to create a file for present day velocities > was: > > > > 1. > > > >     (1)  Load the Reconstruction Tree > > > > 2. > > > >     (2)  Load the Dynamic Polygons > > > > 3. > > > >     (3)  Generate a grid for the velocity output with Features → > >     Generate Velocity Domain Points > > > > 4. > > > >     (4)  This will show velocity vectors for the grid points. Export > >     through Reconstruction → Export > > > > I hope that gets you started, > > Anne > > > > > > > >> On 26 Oct 2017, at 08:20, Maxwell Rudolph > > >> >> wrote: > >> > >> Eleonora, > >> There is a 'depth dependent' material model that allows you to > >> prescribe a depth-dependent viscosity prefactor to any of the other > >> material models. > >> > >> Max > >> > >> On Wed, Oct 25, 2017 at 6:41 AM, Eleonora Ficini > >> > >> wrote: > >> > >>     Hello everyone, > >>     I am a PhD student, I recently started to use ASPECT and I have > >>     two different questions: > >> > >>     1) I would like to know if someone tried to include plate > motion > >>     reconstruction (from GPlates) into ASPECT. If yes, what kind of > >>     files does ASPECT need? It seems that the manual doesn't > mention > >>     the correct way to built the velocity/time file. > >> > >>     2) In a global spherical model, how is the layered rheological > >>     structure (especially regarding a 100 km thick lithosphere)? > >> > >>     Thank you in advance for your time and attention. > >> > >>     All the best, > >>     Eleonora > >> > >> > >>     _______________________________________________ > >>     Aspect-devel mailing list > >> Aspect-devel at geodynamics.org > > > > >> > http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel > > >>    >   > > >> > >> > >> _______________________________________________ > >> Aspect-devel mailing list > >> Aspect-devel at geodynamics.org > > > > >> > http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel > > > > > > > > > _______________________________________________ > > Aspect-devel mailing list > > Aspect-devel at geodynamics.org > > > http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel > > > -- > Rene Gassmoeller > http://www.math.colostate.edu/~gassmoel/ > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Aspect-devel mailing list > Aspect-devel at geodynamics.org > http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel > > > ------------------------------ > > End of Aspect-devel Digest, Vol 71, Issue 12 > ******************************************** > > > > > -- > Eleonora Ficini, PhD student > Department of Earth Sciences > Sapienza University of Rome > P.le A. Moro, 5 - 00185, Rome, Italy > > > > > _______________________________________________ > Aspect-devel mailing list > Aspect-devel at geodynamics.org > http://lists.geodynamics.org/cgi-bin/mailman/listinfo/aspect-devel -- Rene Gassmoeller http://www.math.colostate.edu/~gassmoel/ -------------- next part -------------- An HTML attachment was scrubbed... URL: