Issue Comment Events

Projects RADIUSS Home

teaguesterling commented on issue spack/spack#45393.

Whoops! Thanks for catching that. Looks like this one wasn’t really ready to go. Will review and fix….

View Comment

Kangie commented on issue spack/spack#45384.

> probably still takes 3 lines per deprecated version… but not 5. …

View Comment

johnwparent commented on issue spack/spack#45427.

cc @adamjstewart @scheibelp @haampie …

View Comment

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

Yes, this issue was fixed in #3630 and it was first present in a release in v4.6. …

View Comment

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

## Codecov Report…

View Comment

justinlaughlin commented on issue GLVis/glvis#296.

> How about source parameter of plotly.graph_objects.Image, so just storing PNGs and then generating the HTML for interactive plotting? If you include some switch for the files, there could be just a single HTML, so no duplicity of the plotly JS source 😉 . …

View Comment

tzanio commented on issue GLVis/glvis#298.

Okay, thanks guys. I trust you …

View Comment

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

After processing settings (configs), there are a set of calls that lead to: …

View Comment

wspear commented on issue spack/spack#45426.

To clarify, the error also showed up during py-scipy’s install step, but somehow occurred in py-numpy’s package. …

View Comment

Chrismarsh commented on issue spack/spack#43002.

I have had to use the :: syntax to get my packages.yaml to ensure I don’t get the linux uuid: …

View Comment

AcriusWinter commented on issue spack/spack#45373.

======================= SUMMARY: sundials-7.1.1-jr7vkf2 ======================== …

View Comment

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

View Comment

VictorEijkhout commented on issue mfem/mfem#4423.

This problems seems to be fixed in 4.7; I was using 4.4. …

View Comment

tzanio commented on issue mfem/mfem#4423.

Thanks for reporting this. …

View Comment

jandrej commented on issue mfem/mfem#4422.

You choose your element block to be of QUAD9 instead of QUAD4…

View Comment

Hemanta822 commented on issue mfem/mfem#4420.

@v-dobrev I would be very much grateful if you could give me some direction. I noticed you had helped in a similar problem in #80 . Thank you! …

View Comment

karthichockalingam commented on issue mfem/mfem#4406.

Hello @vladotomov …

View Comment

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

@milroy, is this one fixed and ready to close or do we have something pending here?…

View Comment

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

## Codecov Report…

View Comment

lindstro commented on issue LLNL/zfp#240.

You’ve included a lot of code, e.g., with support for multiple compression modes. It would help us isolate the issue if you could reduce the 1D example to only the essential code being executed. …

View Comment

rhornung67 commented on issue LLNL/axom#1196.

Folks, could I get another pair of eyeballs (at least) to review this PR?…

View Comment

bgunnar5 commented on issue LLNL/axom#1378.

@LLNL/axom I’m investigating test failures right now and it looks like most of the issues come from the blueos system, specifically because of the use of MATCHER_P from gmock. It looks like Klee also had this problem in the past: https://github.com/LLNL/axom/blob/0cf501c46f17acc56e4ae5890c0571d1848dbe00/src/axom/klee/tests/KleeMatchers.hpp#L14 …

View Comment

adayton1 commented on issue LLNL/Umpire#897.

Should there be a branch targeting main?…

View Comment

artv3 commented on issue LLNL/RAJA#1702.

> Is the kernel name exposed to plugins? …

View Comment

MrBurmark commented on issue LLNL/RAJA#1702.

Is the kernel name exposed to plugins?…

View Comment

adayton1 commented on issue LLNL/CHAI#271.

Thanks, @dtaller and @liu15 !…

View Comment

Chuan1937 commented on issue LLNL/zfp#240.

I continued to test the decompressed data and found that the data values ​​were all 0。 I don’t know how to solve it, I hope someone can give me some help…

View Comment

ilumsden commented on issue LLNL/Caliper#576.

In the future, it might be useful to consider embedding archspec-json if more architecture-specific features are added to Caliper….

View Comment

chu11 commented on issue flux-framework/flux-sched#1253.

oops … wrong place. moving to flux-core…

View Comment

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

Thanks for the review! Setting MWP….

View Comment

victorapm commented on issue hypre-space/hypre#1104.

Hi Paul, I will work on these additions. In the meantime, please let me know if you have any issues with our autotools HIP build …

View Comment

siebrenreker commented on issue LLNL/zfp#238.

Hi @lindstro, would you then also prefer this PR to be targeted to the staging branch?…

View Comment

spencer-gre commented on issue LLNL/hatchet#144.

I’ve added b07fbf3 to this pull request. This commit ensures that all PerfFlowAspect Trace files can be read without manual modification. …

View Comment

davidbeckingsale commented on issue LLNL/blt#341.

Later RAJA releases contain the conditional code in CMakeLists for only adding that flag when appropriate….

View Comment

vessokolev commented on issue LLNL/blt#341.

> > @rrsettgast - this is a problem with GCC and CUDA 10, fixed in CUDA 11. The correct workaround is to add the flag -Xcompiler -mno-float128 to your CUDA compile flags. We already have the workaround for this in RAJA: https://github.com/LLNL/RAJA/blob/develop/CMakeLists.txt#L92 …

View Comment

JanLJL commented on issue LLNL/zfp#235.

Hi Peter, …

View Comment

hmaarrfk commented on issue LLNL/zfp#231.

See #227 or I believe I had a patch: …

View Comment

jaimergp commented on issue LLNL/zfp#231.

I don’t know why it can’t find the Python.h headers. They are there in include. Those CMake functions are now deprecated so maybe it would be a good idea to upgrade them, but I don’t have the time nor the expertise to dive there, sorry….

View Comment

nychiang commented on issue LLNL/hiop#651.

> @nychiang I will be reviving this work in another PR using NAERM GitLab. …

View Comment

cameronrutherford commented on issue LLNL/hiop#651.

@nychiang I will be reviving this work in another PR using NAERM GitLab. …

View Comment

t20100 commented on issue LLNL/zfp#222.

Same issue when building ZFP as part of hdf5plugin with Visual Studio 2022 17.10.3 (MSVC/14.40.33807): /Ob1 fixes the issue as well….

View Comment

william-silversmith commented on issue LLNL/zfp#231.

Just looking at AppVeyor, it kinda looks like the failing runs are using python2.7 (EOL Jan. 1, 2020) and an old pip and so are not finding numpy 2.0 wheels. If its reconfigured to use Python3 and a newer pip is used, it’ll probably work….

View Comment

bgunnar5 commented on issue LLNL/merlin#488.

I had a test fail on a branch of my forked repo for the same reason but I have no idea what’s causing it. I’m going to try removing 3.7 to see if it also happens in other versions when I get the chance…

View Comment

lucpeterson commented on issue LLNL/merlin#488.

I’m not sure why this is failing. It looks like py 3.7 is dying on package install / pip and is cancelling everything else….

View Comment

white238 commented on issue LLNL/blt#693.

No problem. Glad it helped. …

View Comment

drmichaeltcvx commented on issue LLNL/blt#693.

Indeed, after setting set(ENABLE_YAPF OFF CACHE BOOL "") GEOS builds completely. …

View Comment

gonsie commented on issue LLNL/scr#459.

This PR is so outdated that I’m closing it rather than figure out how to bring it up to date. We may want to revisit this some day… but not today….

View Comment

romintomasetti commented on issue LLNL/hatchet#103.

Hi @Julius-Plehn ! Any update on this ? I am using hatchet.GraphFrame.from_timemory, which seems broken. It would be nice to re-enable testing for this reader :wink:…

View Comment

kathrynmohror commented on issue LLNL/scr#590.

@gonsie Are there user facing interfaces that have changed or been added? If so, then yes…

View Comment

hariharan-devarajan commented on issue LLNL/scr#591.

@gonsie I just tested it and it works….

View Comment

jithunnair-amd commented on issue LLNL/hatchet#134.

Closing since py3.12 binaries are being published on PyPI now….

View Comment

jwhite242 commented on issue LLNL/maestrowf#443.

Oh, and one more comment. Having the full string in the match means we shouldn’t have to assume it’s the last line either, so just using the regex.search iterator should find a match on any line; should be safer in case those plugins also allow output after the jobid (would hope not, but easy enough to guard against that)….

View Comment

grondo commented on issue hpc/Spindle#53.

Eh, like I said the naming isn’t critical, by default the Flux job shell will load *.so from the plugin search path, so either fluxspindle.so or libfluxspindle.so would work….

View Comment

mplegendre commented on issue hpc/Spindle#53.

I’m cautious about going to spindle.so for the flux plugin. Spindle already has a libspindle.so for its user interface library, and mixing those names could be confusing. Could we symlink a spindle.so in the flux plugin space to a libspindleflux.so in the spindle space? …

View Comment

BenWibking commented on issue LLNL/maestrowf#441.

> Think this might be what’s adding all that extra output on your cluster: https://slurm.schedmd.com/job_submit_plugins.html with some custom validation/logging messages always spit out (I’ll wager srun and salloc do the same?). Haven’t found anything yet about whether the order is always to dump out all these log messages prior to the job id line, but seems likely given most of this happens before the actual submission. Almost think it might be safer to leave the –parseable option off and have that regex account for ‘Submitted batch job’ prefix on the line so we can be sure the number we detect is actually the one we want? …

View Comment

FrankD412 commented on issue LLNL/maestrowf#441.

I think the Submitted batch job <ID> format was standard if I’m not mistaken. It could be a simple regex for the initial submitted message and then parsing that line. That seems like the easiest fix. …

View Comment