Displaying 2 results from an estimated 2 matches for "comp6".
Did you mean:
comp
2017 Sep 18
0
Q2/R2 ratio in PLSDA
...335, 1.8305, 4.5704, 0.2238, 3.6566, 4.0569, 2.1626,
3.2887, 1.4183, 2.1783, 2.6233, 3.2128), comp5 = c(1.0424,
2.2589, 0, 1.2217, 0, 0, 0, 0, 0, 0, 1.6675, 1.7548, 0, 1.0983,
1.2258, 1.314, 2.9437, 0, 0.9749, 0.8959, 0, 0.9189, 1.5026,
0, 1.0831, 2.2251, 0.8419, 1.1912, 2.2912, 0), comp6 = c(4.0781,
7.2073, 6.0885, 4.9657, 4.0133, 7.6783, 4.2064, 1.6421, 6.6831,
6.8437, 6.5152, 1.4712, 7.048, 4.9872, 4.4658, 1.3119, 10.2047,
4.7551, 3.7564, 4.829, 8.5836, 3.508, 6.0251, 5.1122, 2.2058,
6.8343, 3.9664, 2.005, 6.6678, 2.8081), comp7 = c(0, 0, 0,
0, 0, 0, 0, 0, 0,...
2016 Sep 30
7
libLTO C API stability policy
Hi all,
libLTO is exposing a very “stable” (in the sense of immutable) C API to be used by linkers (and binutils tools) that manipulate bitcode (like when performing LTO).
I’m looking into relaxing the stability concern and design a policy for this API that would allow to deprecate and remove some the APIs exposed here. The MacOS linker (ld64) is one the users of libLTO, but there are others