--
You received this message because you are subscribed to the Google Groups "sanskrit-programmers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sanskrit-program...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Run the repository's read_gretil.py on the file containing the GRETIL text. For some files you may have to filter out some non-verse lines (for this one, patch in diff-amaru_u.htm.patch ; see generate-stats.sh).
I guess it's time for another round of updates on the Sanskrit metre recognizer, as my last reply was on Nov 7, more than six weeks ago.
I have pushed to the website a new version with minor improvements (and some regressions, still to fix), currently serving at http://1d.sanskritmetres.appspot.com/ (The previous version is still the default, available at http://1b.sanskritmetres.appspot.com/ for a while longer.)
The minor improvements have been mostly driven by running the code over a few GRETIL texts, a table summarising the results of which is on the main page as well. In fact, what occupied me for a long time was trying to fix up the GRETIL text of Bhartṛhari's Śataka-traya, by comparing each metrically questionable verse against variants in the excellent critical edition produced by DD Kosambi in 1948 and available on DLI. (See diff-bharst_u.htm.patch.) However, after a lot of time spent and still being only a little about half-way through, I gave up for now, became a bit more liberal with declaring a verse as identified, and proceeded to other texts. I plan to return to this too.
I am aware of several still-existing deficiencies, tracked at https://github.com/shreevatsa/sanskrit/issues?state=open .Most notably, it still doesn't have thousands of metres, only dozens. However, after looking at a few actual texts (such as Kirātārjunīya and Raghuvaṃśa) I am finally convinced of the need to include at least some of the obscure metres as well, and will get to adding all of them shortly. The work done by Dhaval and Vishvas will be helpful here.
In light of some previous comments, I'd like to make a couple of things clear:(1) The web interface is intended for human users individually inputting a single verse. Thus I trust them to take care of things like removing extraneous junk that is obviously not part of the verse and can confuse the recognizer (like a, b, c, d for pādas).
I am not keen on tampering with the user's input too much for the web interface. (For the reasons, see (2) below.) When you want to scan an entire messy text with the mess in a known pattern, you can always programmatically remove it, and run the metre recognizer offline. (See read_gretil.py.)
(2) There are two tasks the ideal metre-recognizing interface should do: identification and validation. The former is making a best guess on a verse assuming it's in some known metre (possibly with faults); the latter is to verify whether a given verse actually satisifies all the constraints. Imagine someone composing a verse, or someone checking if a verse is correct. I don't want to go too liberal (especially silently), and start allowing verses that don't actually fit the metre properly, on the web interface.
In such cases, the ideal thing I'd like is to show the best-guess metre, while also highlighting exactly what is off.
I'll reply here again when the metres are all added, and the major issues are fixed.
Then I'll request another round of testing and comments.
--
You received this message because you are subscribed to the Google Groups "sanskrit-programmers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sanskrit-program...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
git clone https://github.com/shreevatsa/sanskrit.git -b metrical-scan new_directory
git initgit remote add gh https://github.com/shreevatsa/sanskrit.gitgit pull gh metrical-scan
python read_gretil.py bharst_u.htm
--
You received this message because you are subscribed to the Google Groups "sanskrit-programmers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sanskrit-program...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
On Tue, Dec 24, 2013 at 10:10 AM, Shreevatsa R <shree...@gmail.com> wrote:
If you have trouble with any step (other than Windows-specific ones like how to install a Terminal or Python on Windows, about which I wouldn't know anything... but I assume that developers who choose to use Windows have basic things like this set up somehow), feel free to ask again.
--
You received this message because you are subscribed to the Google Groups "sanskrit-programmers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sanskrit-program...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "sanskrit-programmers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sanskrit-program...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
me too waiting for the updates..Wish that shreevatsa comes up with frontend also.
On Thu, Mar 6, 2014 at 11:27 AM, Mārcis Gasūns <gas...@gmail.com> wrote:
It's year after. Eagerly waiting for updates. Ready to test it.
On Saturday, 28 December 2013 20:22:55 UTC+4, dhaval patel wrote:tried to document the cygwin way for the windows users who are in no know how of using python.
--
You received this message because you are subscribed to the Google Groups "sanskrit-programmers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sanskrit-programmers+unsub...@googlegroups.com.
One year anniversary past.