search for: filter1

...t. I bet there is a method to draw multiple gates through the panel-function, as curv1filter can also identify multiple peaks automatically and draw them into a densityplot... This script works for  xyplot but not for densitylot:     library(flowCore)     library(flowViz)     data(GvHD)     Filter1        <-    rectangleGate(filterId="Filter1", "FSC-H" = c(0, 200))     Filter2        <-    rectangleGate(filterId="Filter1", "FSC-H" = c(300, 400))     xyplot( `SSC-H` ~ `FSC-H` , data=GvHD[[1]],         panel = function(...) {             panel.xy...

...e index of df$M. When I run the following loop as it is vs. df[,D] and df[,M] replaced with df$D and df$M there is a real big time difference in completion (with the latter being significantly faster). Is there an easy reason why and how I could speed up access? for (m in 1:12) { for (d in 1:31) { filter1<-((df[,D]==d) & (df[,M]==m)) if(sum(filter1)>0) { ctr<-ctr+1 dates[ctr]<-paste(as.character(d),as.character(m)) } } } Thanks... [[alternative HTML version deleted]]

..._next_config_complete *next, void *nxdata); > const char *config_help; > > void * (*open) (int readonly); Is it conceivable that opening a filter may want to read data from the underlying backend? Do we have guarantees on lifecycle ordering across the chain (if the command line uses filter1 filter2 plugin, we open plugin first, filter2 second, filter1 last; then close in reverse order)? > nbdkit-filter.pod > > > Different filters can be stacked: > > NBD ┌─────────┐ ┌─────────┐ ┌────────┐ > client ───▶│ filter1 │───▶│ filter2 │── ─ ─ ──...

...complete in inner-to-outer order. */ log_verify_seen_in_order ("testlayersfilter3: open readonly=0", - "filter3: test_layers_filter_open", "testlayersfilter2: open readonly=0", - "filter2: test_layers_filter_open", "testlayersfilter1: open readonly=0", - "filter1: test_layers_filter_open", "testlayersplugin: open readonly=0", "test_layers_plugin_open", + "filter1: test_layers_filter_open", + "filter2: test_layers_filter_open", + "filter3: te...

Hi , I want to be able to filter out results using a string. I'm running an automated script that reads a list of filters I get from an external source and applys them to my data frame consecutively. For example I want to get : data[protocol==1], data[protocol==2] ... If I define filter1 <- "protocol==1" (as a string) filter2 <- "protocol==2" ... How can I use these variables to choose subsets ? I managed to find a very awkward method by using a function that calls a formula (and using as.formula() for the string I want to get), but I would love to find...

Can you see if this fixes the include problem? Rich.

...behaviour of the plugin. This manual page describes how to create an nbdkit filter. Filters can be used for example to limit requests to an offset/limit, add copy-on-write support, or inject delays or errors (for testing). Different filters can be stacked: NBD client filter1 filter2 plugin request Each filter intercepts plugin functions (see L<nbdkit-plugin(3)>) and can call the next filter or plugin in the chain, modifying parameters, calling before the filter function, in the middle or after. Filters may even short-cut the chain. As...

Hi suppose I have two arrays x1,x2 of dimensions a1,b1,c1 and a2,b2,c2 respectively. I want x = x1 "+" x2 with dimensions c(max(a1,a2), max(b1,b2),max (c1,c2)) with x[a,b,c] = x1[a1,b1,c1] + x2[a2,b2,c2] if a <=min(a1,a2) , b<=min (b1,b2), c<=min(c1,c2) and the other bits either x1 or x2 or zero according to whether the coordinates are "in range" for

....pwrite = test_layers_plugin_pwrite, .flush = test_layers_plugin_flush, diff --git a/tests/test-layers.c b/tests/test-layers.c index 261b9c6..c8d15d2 100644 --- a/tests/test-layers.c +++ b/tests/test-layers.c @@ -349,6 +349,12 @@ main (int argc, char *argv[]) "filter1: test_layers_filter_is_rotational", "test_layers_plugin_is_rotational", NULL); + log_verify_seen_in_order + ("filter3: test_layers_filter_can_multi_conn", + "filter2: test_layers_filter_can_multi_conn", + "filter1: test_layers_filter_c...

I'm still working on another set of patches to have reopen call .finalize/.prepare (so that another filter can safely appear between retry and the plugin), but for tonight, these are the patches I think are ready to go. Eric Blake (4): retry: Handle can_fua and can_fast_zero changes tests: Test retry with different fua/fast-zero flags server: Close backends if a filter's .open fails

...e/nbdkit-plugin.h +test_layers_plugin_la_CPPFLAGS = -I$(top_srcdir)/include test_layers_plugin_la_CFLAGS = $(WARNINGS_CFLAGS) # For use of the -rpath option, see: # https://lists.gnu.org/archive/html/libtool/2007-07/msg00067.html @@ -562,6 +563,7 @@ test_layers_plugin_la_LDFLAGS = \ test_layers_filter1_la_SOURCES = \ test-layers-filter.c \ $(top_srcdir)/include/nbdkit-filter.h +test_layers_filter1_la_CPPFLAGS = -I$(top_srcdir)/include test_layers_filter1_la_CFLAGS = $(WARNINGS_CFLAGS) -Dlayer='"filter1"' # For use of the -rpath option, see: # https://lists.gnu.org/archive...

...ho '/sourcedir/a/file2' >/tmp/excluded.list.tmp #yes this will work: [sender] hiding file sourcedir/a/file2 because of pattern /sourcedir/a/file2 rsync --recursive --perms --delay-updates --files-from=/tmp/filesfrom.list.tmp --exclude-from=/tmp/excluded.list.tmp --delete-excluded --debug=FILTER1 -- ./ ./destdir/ if test -r 'destdir/sourcedir/a/file2'; then echo 'test failed' else echo 'test succeeded' fi #cleanup rm -rf -- destdir sourcedir rm -- /tmp/excluded.list.tmp /tmp/filesfrom.list.tmp I have made a rsync patch(syntax-colored here [1]) in order to squa...

...ent. */ + + /* .default_export methods called in outer-to-inner order. */ log_verify_seen_in_order - ("filter3: test_layers_filter_list_exports", - "testlayersfilter2: list_exports", - "filter2: test_layers_filter_list_exports", - "testlayersfilter1: list_exports", - "filter1: test_layers_filter_list_exports", - "testlayersplugin: list_exports", - "test_layers_plugin_list_exports", + ("testlayersfilter3: default_export", + "filter3: test_layers_filter_default_export", +...

...-to-inner order. */ + log_verify_seen_in_order + ("testlayersfilter3: default_export", + "filter3: test_layers_filter_default_export", + "testlayersfilter2: default_export", + "filter2: test_layers_filter_default_export", + "testlayersfilter1: default_export", + "filter1: test_layers_filter_default_export", + "testlayersplugin: default_export", + "test_layers_plugin_default_export", + NULL); + /* open methods called in outer-to-inner order, but thanks to next * pointer, complete...

...called in order. */ + log_verify_seen_in_order + ("testlayersfilter3: ready_to_serve", + "filter3: test_layers_filter_ready_to_serve", + "testlayersfilter2: ready_to_serve", + "filter2: test_layers_filter_ready_to_serve", + "testlayersfilter1: ready_to_serve", + "filter1: test_layers_filter_ready_to_serve", + "testlayersplugin: ready_to_serve", + "test_layers_plugin_ready_to_serve", + NULL); + /* open methods called in outer-to-inner order, but thanks to next * pointer, complete...

Hi, I have the following code working in a rails 3 view, but it is unfortunately not pure rails code! <% @filter1 = "tr.show1,tr.show2" %> <% @filter2 = "tr.show1" %> <% @filter3 = "tr.show2" %> <form> <p> <input type="checkbox" value=<%=@filter1%> onclick="$ (this).is('':checked'') && $(this.value).ad...

First thing to say is that I need to do a *lot* more testing on this, so this is just an early peek. In particular, although it passed ‘make check && make check-valgrind’ I have *not* tested it against a multi-conn-aware client such as the Linux kernel >= 4.9. This implements NBD_FLAG_CAN_MULTI_CONN, described in the protocol doc as: "NBD_FLAG_CAN_MULTI_CONN: Indicates that

I'm still working my way through the filters before this series will be complete, but this is enough of a start to at least get some feedback on the idea of implementing another NBD protocol extension. Eric Blake (9): server: Internal hooks for implementing NBD_CMD_CACHE plugins: Add .cache callback file, split: Implement .cache with posix_fadvise nbd: Implement NBD_CMD_CACHE

For existing commits, this is almost identical to v1, except that I updated some commit messages and reordered the commits in a somewhat more logical sequence. The main changes are the extra commits: [06/11] plugins: Return NBD_FLAG_CAN_MULTI_CONN from some readonly plugins. - Readonly plugins that can set the flag unconditionally. [09/11] partitioning: Return NBD_FLAG_CAN_MULTI_CONN. [10/11]

Eric: Did you want to take this one any further? It might be one that we save for > 1.18: https://www.redhat.com/archives/libguestfs/2020-February/thread.html#00206 Another thing I've been thinking about for some time is splitting .config_complete into .config_complete + .get_ready (new name TBD). At the moment .config_complete is both the place where we finish processing config, and