Issue Comment Events

Projects RADIUSS Home

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

If you suspect this is an error in SuperLU_DIST, you can create an issue on their GitHub page: https://github.com/xiaoyeli/superlu_dist….

View Comment

luckyqsz commented on issue mfem/mfem#4879.

> Something is inconsistent with the output you posted: you say you had the option -d cuda but the output shows…

View Comment

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

## Codecov Report…

View Comment

tzanio commented on issue mfem/mfem#4882.

This PR is now under review (see the table in the PR description). To help with the review process, please do not force push to the branch….

View Comment

tpatki commented on issue flux-framework/flux-core#6873.

Hi @trws @garlick @grondo: …

View Comment

liruipeng commented on issue hypre-space/hypre#1293.

Hi @victor-decaria-nnl This seems like a thrust issue to me. Not sure if we can do anything in hypre. Thanks…

View Comment

sam-maloney commented on issue flux-framework/flux-core#6838.

I don’t think so… I just have the output saved from this single test failing, and I don’t remember anything catastrophic, haha! Usually if I see lots of tests failing I assume something’s wrong with my build/install and start over, which usually improves things :)…

View Comment

ilumsden commented on issue LLNL/hatchet#163.

After discussing with @michaelmckinsey1, we decided to do the following: …

View Comment

cyrush commented on issue Alpine-DAV/ascent#1550.

View Comment

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

It is used when VISIT_NOLINK_MPI_WITH_LIBRARIES is true (means only executables will be linked with MPI, not libraries)….

View Comment

rfalgout commented on issue hypre-space/hypre#1292.

Try configuring hypre with –enable-mixedint instead. This uses big ints in parts of the code where it is needed and normal ints elsewhere. The return value of hypre_IJVectorGlobalNumRows and hypre_ParVectorGlobalSize will not be an actual big int unless you configure this way or with –enable-bigint. Hope this helps!…

View Comment

bechols97 commented on issue LLNL/RAJA#1832.

Being able to support multiple error/logging messages within the same loop is definitely a use case that we would want to support. This is something that the library I help maintain uses. …

View Comment

najlkin commented on issue GLVis/glvis#342.

For setting just index, you may use the aforementioned scripts. The script would look like this roughly (let us say script.gvsh):…

View Comment

sundials-users-github-account commented on issue LLNL/sundials#711.

Hi Dan, …

View Comment

yanfeit commented on issue GLVis/glvis#342.

Thanks for all the replies. These are all very helpful. I have change the initial setup from “jet-like” to “viridis” through …

View Comment

rhornung67 commented on issue LLNL/axom#1561.

I’ll work on something for the dev guide and put up a PR….

View Comment

gunney1 commented on issue LLNL/axom#1561.

How about something like this?…

View Comment

codecov[bot] commented on issue flux-framework/flux-sched#1355.

## Codecov Report…

View Comment

mkre commented on issue LLNL/hatchet#162.

Thanks, that helps to circumvent the error, and wasn’t quite obvious from the documentation. However, now I have issues seeing all the relevant data in the Hatchet output with my real-life application. Not sure if it is related to the issue reported above. Please let me know if I should create a separate ticket for that….

View Comment

lindstro commented on issue LLNL/zfp#269.

@vicentebolea Not sure what these ndarray errors are. I’m busy over the next few days but will take a closer look as soon as I can….

View Comment

jwake commented on issue LLNL/zfp#268.

For what it’s worth, I managed to get the parallel decoder working fairly well on CUDA (~70GB/sec on an A100 with buffers in device memory, though I’ll note I’m only testing 3D at the moment) between this change and manually bodging the stream_rseek call at the end of zfp_internal_cuda_decompress to reset the pointer offset without trying to read from the stream (in my case, the stream was in device memory, so rseek internally trying to read the buffer would fail; short of a separate device-aware bitstream implementation I’m not sure what the best approach here would be from an API standpoint), and then manually saving/restoring the appropriate index data externally after compression / before decompression. I did note that further compressing the index data with eg. LZ4 or Deflate netted a further ~15% size improvement on the index data but with appropriate granularity the index was already pretty small compared to the bulk of the compressed data. …

View Comment

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

Ok, that sounds like a failure misidentified as ENOMEM then… will have to look and see if we have some that might go rogue….

View Comment

grondo commented on issue flux-framework/flux-sched#1372.

The sar data is sill there, here’s a report on memory around that time:…

View Comment

sam-maloney commented on issue flux-framework/flux-sched#1373.

On my Rocky9 VM with 8 cores and default configuration (just running flux start -s3), I get successful allocations for the following (with the jobspec resource dict in the first lines followed by the allocated R_lite and nodelist arrays in the second lines):…

View Comment

ksaurabh-amd commented on issue LLNL/Umpire#966.

Hi,…

View Comment

devreal commented on issue LLNL/Umpire#822.

We’re running into issues with missing namespaces as well. We want to include Umpire through CMake FetchContent but the clashes makes this more complicated than it needs to be. @evaleev can adds details if needed….

View Comment

gzagaris commented on issue LLNL/Umpire#964.

> We don’t currently have a way to “destroy” an allocator. The release function will deallocate all of the memory iff it is not currently used (e.g. it will deallocate all the chunks that the pool has allocated provided they aren’t being used to satisfy a user allocation request)…

View Comment

djagodzinski commented on issue LLNL/maestrowf#430.

Hi @jwhite242,…

View Comment

dtaller commented on issue LLNL/maestrowf#430.

Hi @djagodzinski . No, unfortunately I have not pushed this. I ended up not doing a scaling study on the machine with the PBS scheduler. Perhaps in the future, but I don’t have plans to pursue this now. You might be better off emailing one of the project owners who works at LLNL to ask….

View Comment

daboehme commented on issue LLNL/Caliper#636.

Hi @adayton1, I think it fixed a segfault that could happen when tool_init() was called before the map was initialized….

View Comment

adayton1 commented on issue LLNL/Caliper#636.

What symptoms did this fix?…

View Comment