similar to: [Bug 14109] New: Support Custom Fuzzy Basis Selection Algorithm

https://bugzilla.samba.org/show_bug.cgi?id=4056 Summary: Option to look for fuzzy basis files in --*-dest directories Product: rsync Version: 2.6.9 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned@samba.org

https://bugzilla.samba.org/show_bug.cgi?id=12527 Bug ID: 12527 Summary: Sender waits for timeout when fuzzy basis file found Product: rsync Version: 3.1.2 Hardware: All OS: All Status: NEW Severity: critical Priority: P5 Component: core Assignee: wayned at samba.org

https://bugzilla.samba.org/show_bug.cgi?id=10581 Summary: --fuzzy-delay and --fuzzy-limit for fuzzy match tuning 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: samba at

https://bugzilla.samba.org/show_bug.cgi?id=12489 Bug ID: 12489 Summary: --fuzzy --fuzzy does not work with daemon Product: rsync Version: 3.1.2 Hardware: All OS: All Status: NEW Severity: critical Priority: P5 Component: core Assignee: wayned at samba.org Reporter:

https://bugzilla.samba.org/show_bug.cgi?id=12498 Bug ID: 12498 Summary: --fuzzy --fuzzy hugely impacts performance even if its' not needed Product: rsync Version: 3.1.2 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core

I've identified a situation where the combination of --fuzzy --fuzzy (yes: two of them) and --link-dest is not behaving as I'd expect. I'm first wondering if my expectation is wrong. Assuming that it is not, then I'm wondering how best to figure out the problem. The double use of --fuzzy is based upon https://bugzilla.samba.org/ show_bug.cgi?id=4056 which should be present on

Hi guys, Is there some way of getting ferret matches string, when i do a fuzzy search? The scenario is this: 1. The user search for ''show'' 2. Nothing was found 3. So I do a fuzzy search, passing ''show~'' 4. It gives me somes results, most of all was matched with ''showcase'' 5. So I want to tell the user that: Nothing was found with

I''m having trouble getting fuzzy searches to work with multiple search terms. Let''s say searching ''foo'' returns results, ''bar'' returns results and ''foo bar'' returns results. When I do this fou~ bar~ it returns nothing. This, however, works fine: fou~ bar I want the fuzzy search to apply to each word, and this seems to

Hi. I didn''t notice if topic has already been discussed, but I was wondering if there was a way to make ferret match only part of a search term. My initial thought was some sort of filter, but I''m unsure of where to begin. An example in the comments of the acts_as_ferret tutorial at RailsEnvy (http://www.railsenvy.com/2007/2/19/acts-as-ferret-tutorial) suggests: To return the

Hello. Forgive my ignorance if this has been covered. I searched through the archives and didn''t find anything. All the blogs, tutorials, documentation I''m reading on acts_as_ferret say that to use fuzzy searching, I simply append a ~ to my query. I''m using Ferret 0.11.3 and the newest (should be) acts_as_ferret plugin. I can only get perfect matches to show up

Hi there, I''d like to be able to tune the results of a Fuzzy search in a rails application. I''ve tried setting the following in my environment.rb file. Ferret::Search::FuzzyQuery.default_min_similarity = 0.75 Ferret::Search::FuzzyQuery.default_prefix_length = 2 When I go into the console, I can see those values as the default but when I run a search like

There are certain queries that I can execute that will cause a completely repeatable segmentation fault at the point where the search or search_each leaves my control and goes into the ferret libraries. I tried deleting my indexes and recreating them, and even so the exact same queries seg fault repeatedly after. Usually a one character change will make them succeed. Changing away from a

Hello, My Ferret integration has gone quite well. I''m now returning all the results I need from two models using "id_multi_search" and combining the results in the view using a couple of partials. Is there any way that I can turn on fuzzy searching? Would fuzzy searching pick up basic spelling mistakes such as "Bnadit" instead of "Bandit" my experience

I just submitted this to Trac, including a proposed fix. I''ve never really used Trac before, so hopefully I did the right thing. Anyway, in case anyone else runs into this, the problem is that fuzzy search fails if some of your saved fields are larger than Ferret::Search::TYPICAL_LONGEST_WORD_IN_INDEX. This won''t happen in all cases where your fields are larger (for example,

Hi, I''ve got a question about FuzzyQueries. Say I''m doing a search for people by name, and I want to allow fuzzy results if there aren''t enough hits with a regular query. This is easy enough; just redo the search with the fuzzy query if original_results.total_hits is less than some threshold. However, I would like the exact-match results to have a higher score

Ein eingebundener Text mit undefiniertem Zeichensatz wurde abgetrennt. Name: nicht verf?gbar URL: <https://stat.ethz.ch/pipermail/r-help/attachments/20130611/09dcb017/attachment.pl>

Does anybody know of aything that will help me do Quantitiative Comparative Analysis (QCA) and/or Fuzzy set analysis?? Or failing that Quine? ta rg Prof R Gott Durham Univesrity UK

Hi the list, Using flextClust, we can cluster data using k-mean with some user-define distances. Is there something similar for fuzzy k-means ? Christophe

https://bugzilla.samba.org/show_bug.cgi?id=1488 Summary: rusty-fuzzy.diff lacks a new file Product: rsync Version: 2.6.2 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: egmont@uhulinux.hu QAContact:

I''m using Geokit gem to query mappable records within some distance to a mappable user. When geocoding an address such as "Madrid", lat&lng represent a point, in this case the center of the city. Suppose I have some records with location "Madrid", which are mapped with lat & lng to the center of the city. When querying for the closest record, the inaccuracy