Issue Comment Events

Projects RADIUSS Home

colmenaresj commented on issue mfem/mfem#4258.

thank you for clarifying…

View Comment

jandrej commented on issue mfem/mfem#4258.

If the mesh is actually distributed, the element numbers don’t match on each MPI rank. That part of the algorithm is basically missing. gslib knows which element it found on what MPI rank but the gather/scatter requires a custom data package to be communicated. We’re currently trying to get gslib to accommodate that….

View Comment

jordialcaraz commented on issue spack/spack#43790.

Any other comments? …

View Comment

spackbot-app[bot] commented on issue spack/spack#43830.

View Comment

jack-morrison commented on issue spack/spack#43830.

@spackbot fix style…

View Comment

tomstitt commented on issue mfem/mfem#3844.

Thank you @sebastiangrimberg for fixing the unit tests! I completely neglected those =| …

View Comment

v-dobrev commented on issue mfem/mfem#4172.

> Perhaps we could put the commit (2e37f2c) fixing (p)minamal-surface.cpp here? 🤔 …

View Comment

mlstowell commented on issue mfem/mfem#4254.

Hi, @Raghavendra0117, …

View Comment

milroy commented on issue flux-framework/flux-sched#1176.

Thanks for the detailed and helpful feedback @trws and @garlick! Setting MWP….

View Comment

trws commented on issue flux-framework/flux-sched#1176.

Bounced the go test runner, looks like it failed to fetch the image for some reason. Feel free to set MWP @milroy, great stuff!…

View Comment

codecov[bot] commented on issue flux-framework/flux-core#5911.

## Codecov Report…

View Comment

grondo commented on issue flux-framework/flux-core#5911.

Thanks! And thanks for catching the original error @wihobbs. I’ll set MWP now….

View Comment

garlick commented on issue flux-framework/flux-core#5899.

Thanks! Setting MWP….

View Comment

biagas commented on issue visit-dav/visit#19465.

@vijaysm that might be helpful, but perhaps other developers more familiar with the MOAB plugin could say for certain….

View Comment

vijaysm commented on issue visit-dav/visit#19465.

> Moab requires lapack, which wasn’t installed in the container from which I built the distro….

View Comment

jacksono1762 commented on issue visit-dav/visit#19210.

Fresh install of 3.4.1 on Ubuntu 22 has fixed this issue…

View Comment

BenWibking commented on issue visit-dav/visit#19413.

Just after I posted that, I did some more digging and I think it’s a CMake environment variable issue. Testing a possible fix now….

View Comment

iulian787 commented on issue visit-dav/visit#19465.

Thank you Kathleen, …

View Comment

garlick commented on issue flux-framework/flux-sched#1186.

I’ll go ahead and set MWP then, thanks….

View Comment

S-o-T commented on issue LLNL/zfp#230.

> We early on anticipated the potential to vary compression parameters spatially, perhaps even from one block to the next, and in that case the overhead of storing compression parameters becomes large. …

View Comment

lindstro commented on issue LLNL/zfp#230.

As mentioned above, one rationale is that the consumer may not want to organize the data the same way the producer does. In fact, I cannot think of a case where the consumer, which processes the data, does not know how it wants the data to be organized. Can you think of a scenario where it would be beneficial to have the producer dictate the data layout for the consumer? In the case of a code processing 2D vector fields, the consumer needs to know if the data layout is float field[ny][nx][2] or float field[2][ny][nx] (or some other permutation) so it can index the multidimensional field properly. If the code is written with one of these conventions, it will fail if the data producer mandates the other convention. While one can write such a code using strides (e.g. field[stride_x * x + stride_y * y + stride_c * c] to access vector component c at (x, y)), oftentimes you want to use some container class like a NumPy array whose strides are given by the container, not the data producer. …

View Comment

adayton1 commented on issue LLNL/axom#1307.

Looks like a lot of the differences disappear with a really small tolerance (EPS = 1e-50)….

View Comment

adrienbernede commented on issue LLNL/Umpire#875.

Ready for review….

View Comment

jvwilliams23 commented on issue LLNL/lbann#2433.

Quick question, how much extra overhead do you expect the environment variable LBANN_NO_INPLACE=1 to create? I am seeing a significantly lower performance compared to pytorch (approx 3.5 days compared to 1 day for 1M iterations through my GAN)….

View Comment

stgeke commented on issue LLNL/conduit#1275.

In this case we can close it. I was just using what Ascent develop is using by default. …

View Comment

cyrush commented on issue LLNL/conduit#1275.

@stgeke …

View Comment

adrienbernede commented on issue LLNL/CARE#255.

@adayton1 this is ready for review !…

View Comment

slabasan commented on issue LLNL/hatchet#123.

Try running with CALI_LOG_VERBOSITY=1 CALI_CONFIG=hatchet-sample-profile ./app and see if you are getting any errors. If you do hatchet-region-profile and run cali-query on it, is the behavior the same?…

View Comment

PhilipDeegan commented on issue LLNL/hatchet#123.

Hi @slabasan …

View Comment

cielling commented on issue LLNL/Caliper#536.

Hi @daboehme, I wanted to check in to see when you/the Caliper team will have time to look into the append option? Thanks!…

View Comment

jameshcorbett commented on issue LLNL/scr#589.

Ok it took a lot of trial and error (some nodes just wouldn’t die on command) but I finally got a solid test of this and it seems to work! Ready for review now @mcfadden8 …

View Comment

jwhite242 commented on issue LLNL/maestrowf#424.

> actually, just had another thought that might fit nicer, expanding it and making the value more of a ‘oneOf’ type, so either value or expression, making it more clear that there’s two types and avoiding having to do greedy parsing on things to figure it out on our end …

View Comment

chapman39 commented on issue LLNL/hiop#684.

I do not have permission to merge this PR, but it is finished….

View Comment

jw447 commented on issue LLNL/zfp#202.

Yes, my LD_LIBRARY_PATH points to …

View Comment

cameronrutherford commented on issue LLNL/hiop#684.

> Seems like I’m missing some permissions …

View Comment

TOMATOFGY commented on issue LLNL/zfp#229.

I think I have a terrible misunderstanding here, as I did not fully grasp the purpose of the program. Thank you for taking the time to provide a helpful response to this issue. …

View Comment

pelesh commented on issue LLNL/hiop#370.

> @pelesh do you remember the context of this feature? …

View Comment

v-dobrev commented on issue GLVis/glvis#274.

> Like many visualization applications GLVis consists of multiple threads / workers that does different things, is that correct? …

View Comment

altineller commented on issue GLVis/glvis#274.

> I’m not really sure if it is possible to use an SDL2 application (GLVis) inside a Qt application (your application). Maybe you can check the SDL2 forums and issues, see https://www.libsdl.org. …

View Comment