search for: cows

--- configure.ac | 5 + filters/Makefile.am | 4 + filters/cow/Makefile.am | 65 +++++++ filters/cow/cow.c | 392 ++++++++++++++++++++++++++++++++++++++ filters/cow/nbdkit-cow-filter.pod | 162 ++++++++++++++++ tests/Makefile.am | 6 + tests/test-cow.sh | 98 ++++++++++ 7 files changed, 732

Eric, you'll probably find the design "interesting" ... It does work, for me at least. Rich.

It would appear that using :include on a model that has_many with an :order on another model makes it so that the order is ignored. Is this supposed to happen? Strikes me as odd behavior. For example class Farmer < ActiveRecord::Base has_many :cows, :order => ''position'' end class Cow < ActiveRecord::Base acts_as_list :scope => :farmer end If I do Farmer.find(:first).cows I get the correct cow order. If I do Farmer.find(:first, :include => ''cows'') then I get the wrong cow order. Any ins...

The blocksize filter already rounds sizes down, to avoid having to special-case a partial action at the end of an unaligned file. But our current behavior for cache and cow is not similarly careful, and can end up causing errors by passing a too-large count to the plugin. The bulk of our plugins are somewhat safe, in that they either fail the pread (for example, the file plugin gets a short read

In xyplot, I would like to get the "data into the panel function" in the following sense: Consider xyplot(scc~time|cowidp, data=cow.s,type=c("l"), panel=function(x,y,subscripts,...){ panel.xyplot(x,y,...) vvv<-cow.s[which(!is.na(cow.s[subscripts,"mastreat"])),"time"] panel.abline(v=vvv,col="red",lwd=2) } ) If I want to use a

The cow filter doesn't support trimming and we should assume the underlying plugin is fully allocated too. Note that both of these limitations might be lifted with a more advanced filter implementation. However we ought to support this in future because xz files contain sparseness information, so add a note. --- filters/cow/cow.c | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-)

...nimal,Mammal and Cow controllers with the scaffolding, just to test and to fill up the Animal table. I can see the "type" column getting it''s value set with the class name. So far, soo good. Now, since listing Animals is showing all animals in the table (including Mammals and Cows) i thought that listing Mammals would show me all Mammals *and* Cows, but i see only recods marked "Mammal" in the "type" column (and no Cows). I understand that Rails doesn''t select descendants of a class when listing it''s elements, and i understand it cou...

Here's the patch (on top of the preceeding one) which uses a bitmap instead of SEEK_DATA. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org --4VrXvz3cwkc87Wze

I want to eliminate the COW feature on all of my OS files. It is a nice feature for user files, but I don''t see a clear benefit for the actual OS files. And I suspect that COW induced fragmentation is causing or aggravating problems with my system including the boot open_ctree problem. I had planned to recursively chattr these files to "nodatacow" status but then I ran

Hi David, --use-cow seems to be quite stable on all variations of tfp (xgl, aiglx, nvidia), I think it was the plan to default-enable it. Do you think it's ready for that? Want a patch? -- Hanno B?ck Blog: http://www.hboeck.de/ GPG: 3DBD3B20 Jabber: jabber@hboeck.de -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type:

When using a filter that rounds up to alignment boundaries, the tail bytes of the plugin are difficult to access correctly. Rather than duplicating lots of code already in the truncate filter, it's easier to just make the other filters default to rounding down and add doc links on how to round up instead. Eric Blake (2): blocksize: Lift restriction against 0-size file cache, cow: Round

These are used at various places in the code already. This refactoring simply moves them to a common header file and should have no other effect. --- common/include/rounding.h | 59 +++++++++++++++++++++++++++++++++++++ filters/cache/Makefile.am | 3 +- filters/cache/cache.c | 2 +- filters/cow/Makefile.am | 3 +- filters/cow/cow.c | 2 +- filters/truncate/truncate.c

Does lme prediction work correctly with poly() terms? In the following simulated example, the predictions are wildly off. Or am I doing something daft? Milk yield for five cows is measured weekly for 45 weeks. Yield is simulated as cubic function of weekno + random cow effect (on intercept) + residual error. I want to recover an estimate of the fixed curve. ############### library(nlme) set.seed(1) ncows <- 5; nweeks <- 45; week <- 1:nweeks mcurve <- 25 + 0.8...

Since we're using ({ .. }) gcc/clang extension, let's rewrite the rounding.h change too. Rich.

Hello guys, I have these models class Farmer < ActiveRecord::Base has_many :cows end class Cow < ActiveRecord::Base set_table_name :cows belongs_to :farmer end ... graph = Farmer.find(x) # Retrieves four cows of x graph.cows[1].name = "Trottolina" graph.save while adding a new cow to collection works perfectly fine, ActiveRecord doesn'...

When compiling on armv7 it becomes clear from the compiler warnings that the current code is wrong. The bitmap has to be allocated in virtual memory, so use size_t to describe the length of the bitmap. When changing the length of the bitmap, compute the new size as an unsigned 64 bit int, and then check whether or not it is too large to fit into size_t before casting it. ---

Dear R-gurus, I am pretty much new on R. I am trying to to do a repeated analysis of a linear mixed model with R, and I consistently fail... The problem is: Cow is the random factor, treatment is the fixed factor. The dependent variable is milk yield, which is measured several times (repeatedly over time), thus there is another variable which is time (i.e. week). The model would be

v1 was here: https://www.redhat.com/archives/libguestfs/2019-September/msg00100.html In v2 I've changed the patch so it avoids calling realloc at all in this case. The patch is a bit longer this way. But I don't see any other alternative if we are to avoid having a "realloc wrapper" of some kind that we use everywhere, which I guess we should avoid because it makes plugins

The following commands: nbdkit -fv --filter=cow memory size=512 --run 'qemu-img info $nbd' nbdkit -fv --filter=cache memory size=512 --run 'qemu-img info $nbd' nbdkit -fv --filter=cow null --run 'qemu-img info $nbd' all fail with: nbdkit: memory[1]: error: realloc: Success Initial git bisect pointed to commit 3166d2bcbfd2 (this is not real cause, it merely

Hello, I am trying to fit a nonlinear model of the form of: A*x^b*exp(-c*x) This represents a lactation curve. I have a bunch of cows, so I want COW to be a random effect. I have been trying the following code with very littel success: > fm1 <- nlme(yield ~ A*(DIM^B)*(exp(-C*DIM)), + data = group, + fixed = A + B + C ~ 1, + start = c(A = 20, B = 0.3, C = 0.03)) Does anyone know how...