fenics team mailing list archive

[Anders Logg <logg@xxxxxxxxx>]

On Mon, Apr 22, 2013 at 08:31:23PM +0100, Garth N. Wells wrote:
> On 22 April 2013 20:28, Garth N. Wells <gnw20@xxxxxxxxx> wrote:
> > On 22 April 2013 20:22, Anders Logg <logg@xxxxxxxxx> wrote:
> >> FFC reference data are now stored here:
> >>
> >> https://bitbucket.org/fenics-project/ffc-reference-data
> >>
> >> The following two scripts are used to download / upload the data:
> >>
> >>   ffc/test/regression/download-references
> >>   ffc/test/regression/upload-references
> >>
> >> The download script is not yet run automatically as part of running
> >> the test suite. My suggestion would be to just call the download
> >> script at the beginning of test/regression/test.py.
> >
> > It should be done via rsync, which will require the server to run
> > rsync. This could be used for the DOLFIN mesh data too.
> >
>
> Sorry, thought that this was on fenicsproject.org when reading
> download and upload. So changes should be pulled and pushed?

The references are stored in a git repository on bitbucket. It will
grow over time (hopefully not too fast) and when it gets too big we
can easily restart it.

The push and pull are handled automatically by the two scripts. Try
running the script download-references and you'll get the idea.

The mechanism is very simple. The upload will tag the repository
each time new references are stored. Then the download script will
look for the latest relevant tag (ffc-reference-data-<n>) and look in
the corresponding directory in the data repository. The two
repositories are not linked in any way (using git).

--
Anders