search for: filter2

...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.xyplot.flowset(...)            glpolygon( Filter1 )            glpolygon( Filter2 )         }     )    ...

...nfig_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 │── ─ ─ ──▶│ plugi...

...s called in order. */ + /* open methods called in outer-to-inner order, but thanks to next + * pointer, 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:...

...lts 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 a more efficient way Thank you ! Yzhar Toren, Tel-...

Hi all, is there a function / package in R that provides a function like Matlab's conv2 or filter2 for smoothing a vector- / velocity- field. I unfortunately could not find anything. Thanks a lot.

https://bugzilla.samba.org/show_bug.cgi?id=8666 Summary: --debug=all9 fail Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: chris at onthe.net.au QAContact: rsync-qa at

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

...r 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 an examp...

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

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

..._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/html/libtool/2007-07/msg00067.html @@ -571,6 +573,7 @@ test_layers_filter1_la_LDFLAGS = \ test_layers_filter2_la_SOURCES = \ test-layers-filter.c \ $(top_srcdir)/include/nbdkit-filter.h +test_layers_filter2_la_CPPFLAGS = -I$(top_srcdir)/include test_layers_filter2_la_CFLAGS = $(WARNINGS_CFLAGS) -Dlayer='"filter2"' # For use of the -rpath option, see: # https://lists.gnu.org/archive...

...ge of + * .list_exports. However it would be easier to do by using libnbd + * than open-coding a naive client. */ + + /* .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", + (...

...nt argc, char *argv[]) * than open-coding a naive client. */ + /* .default_export methods called in outer-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&q...

.../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_can_multi_conn", + "test_layers_plugin_can_multi_conn", + NULL); fprintf (stderr, "%s: protocol connected\n", program_name); -- 2.19.2

...c, char *argv[]) "test_layers_plugin_config_complete", NULL); + /* ready_to_serve methods 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&q...

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

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).addClass(''hidden'') || $ (this.value)....

...@ main (int argc, char *argv[]) "test_layers_plugin_config_complete", NULL); + /* get_ready methods called in order. */ + log_verify_seen_in_order + ("testlayersfilter3: get_ready", + "filter3: test_layers_filter_get_ready", + "testlayersfilter2: get_ready", + "filter2: test_layers_filter_get_ready", + "testlayersfilter1: get_ready", + "filter1: test_layers_filter_get_ready", + "testlayersplugin: get_ready", + "test_layers_plugin_get_ready", + NULL); + /* pre...

It's easy to use the sh script to demonstrate that nbdkit is inefficiently calling into .get_size, .can_fua, and friends more than necessary. We've also commented on the list in the past that it would be nice to ensure that when filters call into next_ops, they are not violating constraints (as we've have to fix several bugs in the past where we did not have such checking to protect

...pen-coding a naive client. > */ > > + /* .default_export methods called in outer-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_layer...