Re: [CZT-Devel] Building from CZT snapshot

[Leo F. <leo...@ne...>]

Hi Anthony,

Thanks for sticking with git and its teething problems… we are getting there and hopefully with the new site it will be easy to document for us/myself as well,
then these problems will be rooted out earlier…

--- SectMngmt.

In a nutshell, review the documentation within the top of SectionManager class and in the get / put methods to see how that affects transactions.
We tried to keep the API as seemingness as possible, yet if you use commands you might need to worry about transactions . Details on the features eamil.

The key motivation for transactions came through the handling of large specs (and those memory issues we discussed a while ago).
The point was how / what to reparse-typecheck or not on the transitive dependency chain such that minimal work was done and consistency
was guarantee.

We took a pretty conservative approach (i.e. if inference of consistency isn't possible, assume section is dirty and redo work), yet even that (together
with memory management improvements) improved performance by an order of magnitude (!!!).

The price for that the API got a bit more complicated for certain kinds of commands. In particular those commands where the "scope" of transaction
need to be widened. For instance, LaTeX parsing leads to a plethora of intermediate stages (i.e. latex markup, operator table, newline table, keyword table, etc),
but in particular low-level Unicode scanning, which leads to transactions overlap that would potentially create inconsistency when a section depend
on similar parents (e.g. quite common with those depending on standard_toolkit).

The widening of transaction scope (to ensure consistency)  and at the same time guarantee a minimum amount of re-work possible (i.e. tokenising
and I/O during parsing is the lion's share of the time for type checking), at the price of some adjustment to section management code.

There are various examples throughout CZT on the use of transactions for the section manager you could draw inspiration from, but we ought / will
add this as a key part of its documentation.

--- VCGing

Some tests on VCG do fail and I know about the issue. They come mostly from weird / unusual schema calculus features for tests that there is
no actual implementation for them yet. I then explicitly say "EXCEPTION HANDLED DURING TESTING" so that I don't loose the test case by removing it.
Given they are from weird uses of Z rather than actual ones, I will only implement later on.

--- jUnit

jUnit is indeed unsorted so one cannot rely on declared order. Instead you could use the setup() and tearDown() methods for setting up things like
the section manager.

Best,
Leo


On 9 Apr 2013, at 14:36, Anthony Hall <an...@an...<mailto:an...@an...>>
 wrote:

Thanks Andrius

I’ve changed the url

When I rebuilt I again got VCG test errors. This time, however, when I tried again the build was successful, although a lot of errors flashed past during the VCG testing they seemed to be handled in some way that didn’t prevent the build working.

I’ve just discovered something horrible that may possibly throw light on that. I’m getting a similar problem with my own cztinterface build – tests are failing apparently randomly. The root cause in my case appears to be a feature of JUnit: within a suite it runs tests in whatever order it feels like (and its mood seems to change from run to run). I had assumed and relied on the fact that it ran them in the order I wrote them. I’m surprised that this hasn’t hit me before. Anyway, I wonder if that might be happening in the VCG case as well?

All the best

Anthony


From: Andrius Velykis [mailto:and...@ne...<http://newcastle.ac.uk>]
Sent: 09 April 2013 13:57
To: Anthony Hall
Cc: CZT-Devel
Subject: Re: [CZT-Devel] Building from CZT snapshot

Dear Anthony,

On Tue, Apr 9, 2013 at 12:45 PM, Anthony Hall <an...@an...<mailto:an...@an...>> wrote:
According to git config:
remote.origin.url=git://czt.git.sourceforge.net/gitroot/czt/czt<http://czt.git.sourceforge.net/gitroot/czt/czt>
remote.origin.fetch=+refs/heads/*:refs/remotes/origin/*
The url is what is given in setup.md<http://setup.md>


Yes, sorry, this is the old CZT Git repository path. After the recent move to the new SourceForge platform, the Git repository addresses changed. The read-only access is now `git://git.code.sf.net/p/czt/code`<http://git.code.sf.net/p/czt/code%60>. For write access, check your personal link at http://sourceforge.net/p/czt/code/ when you are logged in to SourceForge.

Let me know if this gets the latest version for you. Here's some info on changing the Git remote URL: http://stackoverflow.com/questions/2432764/how-to-change-a-remote-repository-uri-using-git

We will update the instructions accordingly. Sorry the about misleading instructions in setup.md<http://setup.md> - I forgot to update the documentation after the repository change.

Best regards,
Andrius

------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter_______________________________________________
CZT-Devel mailing list
CZT...@li...<mailto:CZT...@li...>
https://lists.sourceforge.net/lists/listinfo/czt-devel