From: Tim A. <tra...@bu...> - 2016-04-06 03:15:12
|
I am working on implementing a new QoI in GRINS, and as part of that I need to do a rayfire across the mesh. As input, I would have the (x,y) or (x,y,z) coordinates of the starting point on a boundary, and an angle at which to fire across. I was wondering if anyone has attempted something like this before. If so, I would appreciate any insights or code that could get me up and running faster. Thanks! |
From: Derek G. <fri...@gm...> - 2016-04-06 05:31:04
|
There are lots of options here... some more exotic than others. To get started, take a look at our very general and straightforward implementation in MOOSE: https://github.com/idaholab/moose/blob/devel/framework/src/utils/RayTracing.C Derek On Tue, Apr 5, 2016 at 11:15 PM Tim Adowski <tra...@bu...> wrote: > I am working on implementing a new QoI in GRINS, and as part of that I > need to do a rayfire across the mesh. > > As input, I would have the (x,y) or (x,y,z) coordinates of the starting > point on a boundary, and an angle at which to fire across. > > I was wondering if anyone has attempted something like this before. > > If so, I would appreciate any insights or code that could get me up and > running faster. > > Thanks! > > ------------------------------------------------------------------------------ > _______________________________________________ > Libmesh-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libmesh-devel > |
From: Paul T. B. <ptb...@gm...> - 2016-04-06 12:36:33
|
Thanks Derek! Tim: That looks pretty much like the outline we discussed yesterday. All: Would there be interest in having this in libMesh proper? On Wed, Apr 6, 2016 at 1:30 AM, Derek Gaston <fri...@gm...> wrote: > There are lots of options here... some more exotic than others. To get > started, take a look at our very general and straightforward implementation > in MOOSE: > https://github.com/idaholab/moose/blob/devel/framework/src/utils/RayTracing.C > > Derek > On Tue, Apr 5, 2016 at 11:15 PM Tim Adowski <tra...@bu...> wrote: > >> I am working on implementing a new QoI in GRINS, and as part of that I >> need to do a rayfire across the mesh. >> >> As input, I would have the (x,y) or (x,y,z) coordinates of the starting >> point on a boundary, and an angle at which to fire across. >> >> I was wondering if anyone has attempted something like this before. >> >> If so, I would appreciate any insights or code that could get me up and >> running faster. >> >> Thanks! >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Libmesh-devel mailing list >> Lib...@li... >> https://lists.sourceforge.net/lists/listinfo/libmesh-devel >> > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Libmesh-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libmesh-devel > > |
From: Roy S. <roy...@ic...> - 2016-04-06 13:00:43
|
On Wed, 6 Apr 2016, Paul T. Bauman wrote: > Thanks Derek! Likewise! > All: Would there be interest in having this in libMesh proper? If it's general enough for you and if the MOOSE folks agree, then definitely. The only downside I can see is that I'd be tempted to add more APIs for ParallelMesh compatibility and use it to replace some inferior FIN-S code, and I have no time nor funding for either. --- Roy |
From: Derek G. <fri...@gm...> - 2016-04-06 13:15:36
|
I would hold off on putting it in libMesh proper for a bit. I'm actually in the middle of writing a paper on a new ray tracing algorithm that scales out to 10,000 cores (so far). I plan on putting that algorithm into libMesh when I'm finished. That will probably be sometime this summer (I was targeting SC16, but, while I have results... I don't have a finished paper yet for various reasons). You can get started with this simple algorithm for now, but if you were to put it in libMesh I would want to take it back out pretty soon. Derek On Wed, Apr 6, 2016 at 9:00 AM Roy Stogner <roy...@ic...> wrote: > > On Wed, 6 Apr 2016, Paul T. Bauman wrote: > > > Thanks Derek! > > Likewise! > > > All: Would there be interest in having this in libMesh proper? > > If it's general enough for you and if the MOOSE folks agree, then > definitely. > > The only downside I can see is that I'd be tempted to add more APIs > for ParallelMesh compatibility and use it to replace some inferior > FIN-S code, and I have no time nor funding for either. > --- > Roy > |
From: Paul T. B. <ptb...@gm...> - 2016-04-06 13:23:47
|
On Wed, Apr 6, 2016 at 9:15 AM, Derek Gaston <fri...@gm...> wrote: > I would hold off on putting it in libMesh proper for a bit. I'm actually > in the middle of writing a paper on a new ray tracing algorithm that scales > out to 10,000 cores (so far). I plan on putting that algorithm into libMesh > when I'm finished. > > That will probably be sometime this summer (I was targeting SC16, but, > while I have results... I don't have a finished paper yet for various > reasons). > > You can get started with this simple algorithm for now, but if you were to > put it in libMesh I would want to take it back out pretty soon. Cool, sounds good. I don't anticipate needing more than hundreds of cores for the problem of immediate interest, so the more simplistic algorithm will suit us just fine. Tim: Just drop it locally in the QoI you're working on and we can migrate later. Looking forward to seeing your paper, Derek! Best, Paul |
From: David K. <dav...@ak...> - 2016-04-06 13:18:56
|
Forgive my ignorance on this, but I'm not familiar with rayfire, I was hoping someone could enlighten me. Does this refer to raytracing? What are the applications of that in the context of FEA/CFD? Is there a good reference someone can point me to? David On Wed, Apr 6, 2016 at 9:15 AM, Derek Gaston <fri...@gm...> wrote: > I would hold off on putting it in libMesh proper for a bit. I'm actually > in the middle of writing a paper on a new ray tracing algorithm that scales > out to 10,000 cores (so far). I plan on putting that algorithm into libMesh > when I'm finished. > > That will probably be sometime this summer (I was targeting SC16, but, > while I have results... I don't have a finished paper yet for various > reasons). > > You can get started with this simple algorithm for now, but if you were to > put it in libMesh I would want to take it back out pretty soon. > > Derek > On Wed, Apr 6, 2016 at 9:00 AM Roy Stogner <roy...@ic...> > wrote: > >> >> On Wed, 6 Apr 2016, Paul T. Bauman wrote: >> >> > Thanks Derek! >> >> Likewise! >> >> > All: Would there be interest in having this in libMesh proper? >> >> If it's general enough for you and if the MOOSE folks agree, then >> definitely. >> >> The only downside I can see is that I'd be tempted to add more APIs >> for ParallelMesh compatibility and use it to replace some inferior >> FIN-S code, and I have no time nor funding for either. >> --- >> Roy >> > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Libmesh-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libmesh-devel > > |
From: Paul T. B. <ptb...@gm...> - 2016-04-06 13:22:16
|
On Wed, Apr 6, 2016 at 9:18 AM, David Knezevic <dav...@ak...> wrote: > Forgive my ignorance on this, but I'm not familiar with rayfire, I was > hoping someone could enlighten me. Does this refer to raytracing? > Basically, yeah. > What are the applications of that in the context of FEA/CFD? > Our interest is for computing QoIs having to do with lasers (freakin' laser beams!). We'll send you the preprint once we're done. :) Best, Paul |
From: David K. <dav...@ak...> - 2016-04-06 13:32:17
|
On Wed, Apr 6, 2016 at 9:22 AM, Paul T. Bauman <ptb...@gm...> wrote: > On Wed, Apr 6, 2016 at 9:18 AM, David Knezevic <dav...@ak... > > wrote: > >> Forgive my ignorance on this, but I'm not familiar with rayfire, I was >> hoping someone could enlighten me. Does this refer to raytracing? >> > > Basically, yeah. > > >> What are the applications of that in the context of FEA/CFD? >> > > Our interest is for computing QoIs having to do with lasers (freakin' > laser beams!). We'll send you the preprint once we're done. :) > OK, thanks! Frickin' laser beams. I hope the future work somehow involves sharks. David |
From: Derek G. <fri...@gm...> - 2016-04-06 13:26:07
|
BTW: I didn't mean to say you couldn't put this in libMesh! Absolutely, you should feel free. I just wanted you guys to know that something much better is in the pipeline so you don't need to invest much in this code. As for what it's used for... there are various things. The main thing we currently use it for in MOOSE is crack propagation for XFEM methods. Derek On Wed, Apr 6, 2016 at 9:22 AM Paul T. Bauman <ptb...@gm...> wrote: > On Wed, Apr 6, 2016 at 9:18 AM, David Knezevic <dav...@ak... > > wrote: > >> Forgive my ignorance on this, but I'm not familiar with rayfire, I was >> hoping someone could enlighten me. Does this refer to raytracing? >> > > Basically, yeah. > > >> What are the applications of that in the context of FEA/CFD? >> > > Our interest is for computing QoIs having to do with lasers (freakin' > laser beams!). We'll send you the preprint once we're done. :) > > Best, > > Paul > > ------------------------------------------------------------------------------ > _______________________________________________ > Libmesh-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libmesh-devel > |
From: Paul T. B. <ptb...@gm...> - 2016-04-06 13:29:48
|
On Wed, Apr 6, 2016 at 9:25 AM, Derek Gaston <fri...@gm...> wrote: > BTW: I didn't mean to say you couldn't put this in libMesh! Absolutely, > you should feel free. Thanks for the clarification. > I just wanted you guys to know that something much better is in the > pipeline so you don't need to invest much in this code. > Agreed, thanks. We'll just roll something quick and dirty on our end and not pollute libMesh with something half-assed since you have something better in the works. |