Hi, I actually tried ../griffonw run-app but it says "griffon-app does not appear to be part of a Griffon application."
I installed griffon and tried again "griffon run-app" inside of griffon-app, but same error. -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com Solr Training - www.solrtraining.com 25. feb. 2013 kl. 19:51 skrev jmlucjav <jmluc...@gmail.com>: > Jan, thanks for looking at this! > > - Running from source: would you care to send me the error you get (if any) > when running from source? I assume you have griffon1.1.0 installed right? > > - Binary dist: the distrib is created by griffon, so I'll check if the > permission issue (I develop on windows, and tested on a clean windows too, > so I don't face the issue you mention) is known or can be fixed somehow. > I'll update the doc anyway. > > - wt param: I am already overriding wt param (in order to use javabin). > What I didn't allow is to choose the handler to be used when submitting the > query. I guess any handler that does not have <appends>/<invariants> that > would interfere would work fine, I just thought /select is mostly available > in most installations and that is one thing less to configure. But yes, I > could let the user configure it, I'll open an issue. > > xavier > > On Mon, Feb 25, 2013 at 3:10 PM, Jan Høydahl <jan....@cominvent.com> wrote: > >> Cool. I tried running from source (using the bundled griffonw), but I >> think the instructions may be wrong, had to download binary dist. >> The file permissions for bin/vifun in binary dist should have +w so you >> can execute it with ./vifun >> >> What about the ability to override the "wt" param, so that you can point >> it to the "/browse" handler directly? >> >> -- >> Jan Høydahl, search solution architect >> Cominvent AS - www.cominvent.com >> Solr Training - www.solrtraining.com >> >> 23. feb. 2013 kl. 15:12 skrev jmlucjav <jmluc...@gmail.com>: >> >>> Hi, >>> >>> I have built a small tool to help me tweak some params in Solr (typically >>> qf, bf in edismax). As maybe others find it useful, I am open sourcing it >>> on github: https://github.com/jmlucjav/vifun >>> >>> Check github for some more info and screenshots. I include part of the >>> github page below. >>> regards >>> >>> Description >>> >>> Did you ever spend lots of time trying to tweak all numbers in a >> *edismax* >>> handler *qf*, *bf*, etc params so docs get scored to your liking? Imagine >>> you have the params below, is 20 the right boosting for *name* or is it >> too >>> much? Is *population* being boosted too much versus distance? What about >>> new documents? >>> >>> <!-- fields, boost some --> >>> <str name="qf">name^20 textsuggest^10 edge^5 ngram^2 >> phonetic^1</str> >>> <str name="mm">33%</str> >>> <!-- boost closest hits --> >>> <str name="bf">recip(geodist(),1,500,0)</str> >>> <!-- boost by population --> >>> <str name="bf">product(log(sum(population,1)),100)</str> >>> <!-- boost newest docs --> >>> <str name="bf">recip(rord(moddate),1,1000,1000)</str> >>> >>> This tool was developed in order to help me tweak the values of boosting >>> functions etc in Solr, typically when using edismax handler. If you are >> fed >>> up of: change a number a bit, restart Solr, run the same query to see how >>> documents are scored now...then this tool is for you. >>> <https://github.com/jmlucjav/vifun#features>Features >>> >>> - Can tweak numeric values in the following params: *qf, pf, bf, bq, >>> boost, mm* (others can be easily added) even in *<appends> or >>> <invariants>* >>> - View side by side a Baseline query result and how it changes when you >>> gradually change each value in the params >>> - Colorized values, color depends on how the document does related to >>> baseline query >>> - Tooltips give you Explain info >>> - Works on remote Solr installations >>> - Tested with Solr 3.6, 4.0 and 4.1 (other versions would work too, as >>> long as wt=javabin format is compatible) >>> - Developed using Groovy/Griffon >>> >>> <https://github.com/jmlucjav/vifun#requirements>Requirements >>> >>> - */select* handler should be available, and not have any *<appends> or >>> <invariants>*, as it could interfere with how vifun works. >>> - Java6 is needed (maybe it runs on Java5 too). A JRE should be enough. >>> >>> <https://github.com/jmlucjav/vifun#getting-started>Getting started >>> < >> https://github.com/jmlucjav/vifun#click-here-to-download-latest-version-and-unzip >>> Click >>> here to download latest >>> version< >> http://code.google.com/p/vifun/downloads/detail?name=vifun-0.4.zip> >>> and >>> unzip >>> >>> - Run vifun-0.4\bin\vifun.bat or vifun-04\bin\vifun if on linux/OSX >>> - Edit *Solr URL* to match yours (in Sol4.1 default is >>> http://localhost:8983/solr/collection1 for example) [image: hander >>> selection]< >> https://github.com/jmlucjav/vifun/raw/master/img/screenshot-handlers.jpg> >>> - *Show Handerls*, and select the handler you wish to tweak from * >>> Handerls* dropdown. The text area below shows the parameters of the >>> handler. >>> - Modify the values to run a baseline query: >>> - *q*: query string you want to use >>> - *rows*: as in Solr, don't choose a number too small, so you can >> see >>> more documents, I typically use 500 >>> - *fl*: comma separated list of fields you want to show for each >> doc, >>> keep it short (other fields needed will be added, like the id, >> score) >>> - *rest*: in case you need to add more params, for example: sfield, >>> fq etc) [image: query >>> params]< >> https://github.com/jmlucjav/vifun/raw/master/img/screenshot-qparams.jpg> >>> - *Run Query*. The two panels on the right will show the same result, >>> sorted by score.[image: >>> results]< >> https://github.com/jmlucjav/vifun/raw/master/img/screenshot-results.jpg> >>> - Use the mouse to select the number you want to tweak in Score params >>> (select all the digits). Note the label of the field is highlighted >> with >>> current value. [image: target >>> selection]< >> https://github.com/jmlucjav/vifun/raw/master/img/screenshot-selecttarget.jpg >>> >>> - Move the slider, release and see how a new query is run, and you can >>> compare how result changes with the current value. In the Current >> table, >>> you can see current position/score and also delta relative to the >> baseline. >>> The colour of the row reflects how much the doc gained/lost. [image: >>> tweaking a value]< >> https://github.com/jmlucjav/vifun/raw/master/img/screenshot-baseline.jpg> >>> - You can increase the limits of the slider, and if you are satisfied >>> with a value, set it, so it will be set to current value. >>> - Tweak another number... >>> - Tooltips exist in Current (Explain info) and Baseline (pos/score of >>> that doc in Current, and Explain in Score column) >> >>
