search for: nprobe

Hi, Would like to run the software to monitor the quality of the bandwidth. Suggestions welcome? Thank you. Shaun -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20081211/85bd0069/attachment.htm

Dear All, I'm currently doing a project about unsupervised learning, and I'll be using R to analyse a few network traffic datasets downloaded off Andrew Moore's website (http://www.cl.cam.ac.uk/Research/SRG/netos/nprobe/data/papers/sigmetrics/index.html). Could anyone shed some light on how to build a classifier from the training set A, and then use a validation set B to assess the performance of the classifier? I'm able to group these datasets into groups using hclust() and kmeans() etc., but I don't se...

...o support, then would someone please provide link/links to more information on recompiling the centos kernel.src.rpm? Googling I found all kinds of information but it either dealt with the 2.4 branch, 2.6 when it was still in testing (digital hermit), involved other distros (Installing PF_RING and nProbe on Fedora Core 4), or was for stock RedHat Enterprise and although CentOS uses the src.rpms from RedHat, I do not want to assume the compile process is the same and end up shooting myself in the foot. Having a process that can be followed for CentOS 4.3 to add functionality to the stock kernel wou...

Hi, I am interested in using the cast function in R to perform some aggregation. I did once manage to get it working, but have now forgotten how I did this. So here is my dilemma. I have several thousands of probes (about 180,000) corresponding to each gene; what I'd like to do is obtain is a frequency count of the various occurrences of each probes for each gene. The data would look

...nline contexts there. I’m happy to work with you on a encoding format that can be used for both Propeller and pseudo probes. This is our current encoding format: // FUNCTION BODY (one for each uninlined function present in the text section) // GUID (uint64) // GUID of the function // NPROBES (ULEB128) // Number of probes originating from this function. // NUM_INLINED_FUNCTIONS (ULEB128) // Number of callees inlined into this function, aka number of // first-level inlinees // PROBE RECORDS // A list of NPROBES entries. Each entry contains: //...

Hi Rahman, Thanks for sharing the BB-info section proposal which is a shiny idea. I think the BB-info and pseudo probes deal with a similar problem in different spaces, i.e., mapping hardware samples to corresponding basic blocks. In the context of pseudo probes, we much focus on mapping samples back to source-level blocks which is the input to the optimizer. Therefore we are building a