Dear all,
good morning.
I tried converting some PineAPPL grids generated by @scarlehoff for the W+jets 8 TeV measurement (arXiv:1711.03296), but I got the following error:
[giuli@pplxint13 xFitter_EL9]$ RUST_BACKTRACE=full pineappl export ATLAS_WP_JET_8TEV_PT-atlas-atlas-wjets-arxiv-1711.03296-xsec002.pineappl.lz4 Wjets_Wp_pT_8TeV.appl MSHT20nnlo_as118
thread 'main' panicked at pineappl/src/grid.rs:952:29:
not yet implemented
stack backtrace:
0: 0x5557ff302859 - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::hc4439741452ac1a2
1: 0x5557ff0bba83 - core::fmt::write::h4392e9747776afaf
2: 0x5557ff2cacf2 - std::io::Write::write_fmt::h308d1ad615b5d20c
3: 0x5557ff3039e3 - std::sys::backtrace::BacktraceLock::print::h204f8c26e3c76121
4: 0x5557ff303f2f - std::panicking::rust_panic_with_hook::hc7a13f6a77cad139
5: 0x5557ff303a85 - std::panicking::begin_panic_handler::{{closure}}::hdb1cf457123442d6
6: 0x5557ff303a19 - std::sys::backtrace::__rust_end_short_backtrace::h25571fe910c10d94
7: 0x5557ff303a0c - rust_begin_unwind
8: 0x5557ff04a80f - core::panicking::panic_fmt::h1a7ab0e9b5409cee
9: 0x5557ff04a85b - core::panicking::panic::ha317b5b5b8afb83a
10: 0x5557ff10b26d - pineappl::grid::Grid::optimize_using::hcc21f1bdf8fa480f
11: 0x5557ff16b082 - pineappl_cli::export::applgrid::convert_into_applgrid::h0df33c7a4ce8860b
12: 0x5557ff064cef - pineappl::main::h1396849747b6a72a
13: 0x5557ff05f333 - std::sys::backtrace::__rust_begin_short_backtrace::h8c0f77d8b36f93d1
14: 0x5557ff076e74 - main
15: 0x7f43dd4295d0 - __libc_start_call_main
16: 0x7f43dd429680 - __libc_start_main@GLIBC_2.2.5
17: 0x5557ff05c025 - _start
18: 0x0 - <unknown>
Have you ever seen a similar error?
Just for the sake of completeness, I am using the exact same setup as yesterday (master version, related to this issue here: #356 )
Best,
Fra
Dear all,
good morning.
I tried converting some PineAPPL grids generated by @scarlehoff for the W+jets 8 TeV measurement (arXiv:1711.03296), but I got the following error:
Have you ever seen a similar error?
Just for the sake of completeness, I am using the exact same setup as yesterday (master version, related to this issue here: #356 )
Best,
Fra