patch

I have a 3d matrix (3x3x3) , and I need to extract 3d patches (2x2x2) and transform them in vectors. In 2d, simply: I=randi(5,3,3); 2d_patches=im2col(I,[2 2],'sliding'); What about 3d? I=randi(5,3,3,3); 3d_patches= ??? im2col just works in 2d. In 3d I should recombine the vectors 1 and 7 , 2 and 8 , ... Is there any fast function for this task? I do not believe that there is any built-in way to do this. If you need it to be fast, it should be fairly simple to write your own mex-function in c and call it from Matlab. Here is my (quick and dirty) solution: im3col.c: #include <mex.h> void

i have a deployed grails apps on tomcat6 in my client server machine, but the application is still need many fix, so every bug founded or missing feature on client machine, i creating a patch and delivering to client via ftp on .tar.gz file that will replace on deployed folder. i can't send a fully .war files because the apps is big (~80M), so sending a changes .class files is the only option i have. but the process to creating a patch is too time consuming , especially on rebuild the project , cleaning up the target folder and start to compile all files on project. after that i search the

I am trying to provide a simple installer package (MSI) which I want to support with updates (patches) that supersede all previous patches. So I have a MSI V1.0.0 and 2 patches V1.0.1 and V1.0.2. The user should be able to just install the latest patch regardless which previous patches were already applied to the system. My project contains 2 features (Client and Server). The basis of the patch so is always the RTM package (HelloWorld 1.0.msi / HelloWorld 1.0.wixpdb). The generation (build) of all patches work, so the update procedures 1.0.0 -> 1.0.1 and 1.0.0 -> 1.0.2 do, BUT when i try to

I'm trying to use python's mock.patch to implement unit tests with nose. class A: def setUp(self): self.b = 8 #contrived example @patch.object('module.class', 'function', lambda x: self.b) def testOne(self): # do test # Here, patch complains that it doesnt know self (which is correct). What is best way to get this kind of functionality in a clean fashion? I know I can use a global variable, or that I can mock it within the test (but that involves me cleaning up the objects at the end of the test). You cannot use self on method decorator because you are in the class definition and the object

I have a Gradle build script that successfully builds my project and compiles all the artifacts I need. However, in a couple of cases I'd like to give other developers the option to patch some of the files. For example, in one of the archives there's an xml file with information about database hooks - some of the devs use other versions (or even engines) and need to change these before they can use the build output. Instead of having them make changes to a version-controlled file, which they might commit by mistake, I'd like to give them the option to have a local, individual patch file which

I want to automatically generate a series of plots which are clipped to patches. If I try and reuse a patch object, it moves position across the canvas. This script (based on an answer to a previous question by Yann) demonstrates what is happening. import pylab as plt import scipy as sp import matplotlib.patches as patches sp.random.seed(100) x = sp.random.random(100) y = sp.random.random(100) patch = patches.Circle((.75,.75),radius=.25,fc='none') def doplot(x,y,patch,count): fig = plt.figure() ax = fig.add_subplot(111) im = ax.scatter(x,y) ax.add_patch(patch) im.set_clip_path(patch) plt

We are in the process of adapting our build & release procedure of one of our Java based products to support patch / hotfix releases. Today, we deliver a full installation package (which is a set of RPM packages wrapped in an ISO) out of our build pipeline. However, we aim to also support incremental / more fine grained upgrade / patch shipments as well. To keep things simple as an initial step, we plan to have more fine-grained RPM packages and package a subset (only the changed ones in the scope of a release) of these RPMs in a dedicated hotfix ISO along with the full installation ISO. (We