Hi everybody,
The migration of the Dynare subversion server is complete.
Dynare subversion is now accessible at:
https://www.dynare.org/svn/dynare
We migrated the server to a secure connection (it is HTTPS and not HTTP !!); there should be no security warning, since we have bought an official digital certificate from Comodo.
For committing changes, the user accounts and passwords are unchanged; however, for increased security, we should change every individual password in the future. We will do this in due time, when we find a way to securely exchange passwords.
The new layout of the repository is the following:
- trunk/: contains the version under development (formerly known as dynare_v4/)
- branches/: containes the 3.x and 4.0 stable branches
- tags/: contains official dynare releases
You have to download a fresh working copy of the repository (for several technical reasons it is impossible to convert your already existing working copies; sorry for the inconvenience).
With command-line subversion, you should issue the following command:
svn checkout https://www.dynare.org/svn/dynare
Please also note that Dynare++ is now in a separate repository, at address:
https://www.dynare.org/svn/dynare++
The same remarks apply.
Ondra: you can contact me if you want me to setup mail announcements for each changeset, as for the Dynare repository. Please also feel free to reorganize the layout of the Dynare++ repository, since for the moment it only contains a single dynare++ subdirectory.
For the moment there is only a very rough web SVN browser, accessible at the same address than the repositories (type https://www.dynare.org/svn/dynare in your web browser). I will try to setup a more friendly web browser soon.
All the best
Sébastien
Hi Sebastien,
since the last update, the parser doesn't accept empty expression as can
be found in uniform priors when we only put something in p3 and p4, so
we have something like
sig,uniform_pdf,,,0,1;
Best
Michel
Hi Stéphane (and everybody else),
I just committed the change to allow arbitrary expressions in
estimated_params block (and also in estimated_params_init and
estimated_params_bounds).
Previously only constants were allowed there.
This involved more modifications than I initially thought, so please
test it a little bit to make sure that I didn't break anything (I
tested it on fs2000.mod only).
Also note that by the way I fixed a bug when estimated_params_init and
estimated_params_bounds were used in conjunction with correlations of
endogenous variables; I also applied the fix to the 4.0 branch.
Best
Sébastien
Dear Friends,
we would like to organize an internal workshop on Dynare development in
Paris on February 19 and 20, 2009.
In particular, we would like to discuss methods to assess identification
of estimated parameters and issues around estimation of nonstationary
variables. But, this would also be the occasion to review briefly all
development projects.
Please confirm as soon as possible that these dates are possible for you.
Kind regards,
Michel
Hi
According to
http://ubuntuforums.org/showthread.php?t=552453
"the server computer had run out of space!"
Best regards
George
Mob. +44(0)7951415480
artilogica(a)btconnect.com
----- Original Message -----
From: "G. Perendia" <george(a)perendia.orangehome.co.uk>
To: "List for Dynare developers" <dev(a)dynare.org>
Sent: Sunday, December 21, 2008 11:17 AM
Subject: Re: [DynareDev] Dynare subversion server: migration complete
> Hi
>
> I am having difficulties downloading new repository (which I need to do
> before I can commit anything)
>
> I am getting the following error messages
>
> Error: REPORT request failed on '/svn/dynare/!svn/vcc/default'
> Error: Can't find a temporary directory: Internal error
>
> Best regards
>
> George
>
> ----- Original Message -----
> From: "Sébastien Villemot" <sebastien.villemot(a)ens.fr>
> To: "Tommaso Mancini" <tommaso.mancini(a)stanfordalumni.org>;
> <marco.ratto(a)jrc.it>; "Junior Maih" <junior.maih(a)gmail.com>; "Heesun Kiem"
> <HKiem(a)imf.org>; "Gianni Lombardo" <giovanni.lombardo(a)ecb.int>;
> <dev(a)dynare.org>; "Ondra Kamenik" <ondra.kamenik(a)gmail.com>; "Assia
> Ezzeroug" <Assia.Ezzeroug(a)ens.fr>; <Gary.Anderson(a)frb.gov>
> Sent: Friday, December 19, 2008 5:04 PM
> Subject: [DynareDev] Dynare subversion server: migration complete
>
>
> > Hi everybody,
> >
> > The migration of the Dynare subversion server is complete.
> >
> > Dynare subversion is now accessible at:
> >
> > https://www.dynare.org/svn/dynare
> >
> > We migrated the server to a secure connection (it is HTTPS and not HTTP
> !!); there should be no security warning, since we have bought an official
> digital certificate from Comodo.
> >
> > For committing changes, the user accounts and passwords are unchanged;
> however, for increased security, we should change every individual
password
> in the future. We will do this in due time, when we find a way to securely
> exchange passwords.
> >
> > The new layout of the repository is the following:
> > - trunk/: contains the version under development (formerly known as
> dynare_v4/)
> > - branches/: containes the 3.x and 4.0 stable branches
> > - tags/: contains official dynare releases
> >
> > You have to download a fresh working copy of the repository (for several
> technical reasons it is impossible to convert your already existing
working
> copies; sorry for the inconvenience).
> > With command-line subversion, you should issue the following command:
> >
> > svn checkout https://www.dynare.org/svn/dynare
> >
> >
> > Please also note that Dynare++ is now in a separate repository, at
> address:
> >
> > https://www.dynare.org/svn/dynare++
> >
> > The same remarks apply.
> >
> > Ondra: you can contact me if you want me to setup mail announcements for
> each changeset, as for the Dynare repository. Please also feel free to
> reorganize the layout of the Dynare++ repository, since for the moment it
> only contains a single dynare++ subdirectory.
> >
> >
> > For the moment there is only a very rough web SVN browser, accessible at
> the same address than the repositories (type
> https://www.dynare.org/svn/dynare in your web browser). I will try to
setup
> a more friendly web browser soon.
> >
> > All the best
> >
> > Sébastien
> >
> >
> >
> > _______________________________________________
> > Dev mailing list
> > Dev(a)dynare.org
> > http://www.dynare.org/cgi-bin/mailman/listinfo/dev
> >
>
Hi,
Just a note: using my 2nd machine which has the latest Tortoise SVN 1.5.5 to
checkout, I get the following messages (and the same error):
"Command: Checkout from https://www.dynare.org/svn/dynare/trunk, revision
HEAD, Fully recursive, Externals included
Error: Can't find a temporary directory: Internal error
Finished!: "
Best regards
George
----- Original Message -----
From: "G. Perendia" <george(a)perendia.orangehome.co.uk>
To: "Michel Juillard" <michel.juillard(a)ens.fr>
Cc: "List for Dynare developers" <dev(a)dynare.org>
Sent: Sunday, December 21, 2008 5:10 PM
Subject: Re: [DynareDev] Dynare subversion server: migration complete]
> Dear Michel
>
> I did and it is both the new site,
>
> https://www.dynare.org/svn/dynare
>
> and the trunk subdirectory that I have been trying to download from:
>
> https://www.dynare.org/svn/dynare/trunk
>
> but I still have no luck and I am repeatedly getting same error messages:
>
> Error: REPORT request failed on '/svn/dynare/!svn/vcc/default'
> Error: Can't find a temporary directory: Internal error
>
>
> Best regards
>
> George
>
> ----- Original Message -----
> From: "Michel Juillard" <michel.juillard(a)ens.fr>
> To: "George Perendia" <artilogica(a)btconnect.com>; "G. Perendia"
> <george(a)perendia.orangehome.co.uk>
> Sent: Sunday, December 21, 2008 1:35 PM
> Subject: [Fwd: [DynareDev] Dynare subversion server: migration complete]
>
>
> >
> > Hi George,
> >
> > you should have received this message via the Dynare developers email
> list.
> >
> > Best
> >
> > Michel
> >
> > -------- Original Message --------
> > Subject: [DynareDev] Dynare subversion server: migration complete
> > Date: Fri, 19 Dec 2008 18:04:54 +0100
> > From: Sébastien Villemot <sebastien.villemot(a)ens.fr>
> > Reply-To: List for Dynare developers <dev(a)dynare.org>
> > To: Tommaso Mancini <tommaso.mancini(a)stanfordalumni.org>,
> > marco.ratto(a)jrc.it, Junior Maih <junior.maih(a)gmail.com>, Heesun Kiem
> > <HKiem(a)imf.org>, Gianni Lombardo <giovanni.lombardo(a)ecb.int>,
> > dev(a)dynare.org, Ondra Kamenik <ondra.kamenik(a)gmail.com>, Assia Ezzeroug
> > <Assia.Ezzeroug(a)ens.fr>, Gary.Anderson(a)frb.gov
> >
> >
> >
> > Hi everybody,
> >
> > The migration of the Dynare subversion server is complete.
> >
> > Dynare subversion is now accessible at:
> >
> > https://www.dynare.org/svn/dynare
> >
> > We migrated the server to a secure connection (it is HTTPS and not HTTP
> !!); there should be no security warning, since we have bought an official
> digital certificate from Comodo.
> >
> > For committing changes, the user accounts and passwords are unchanged;
> however, for increased security, we should change every individual
password
> in the future. We will do this in due time, when we find a way to securely
> exchange passwords.
> >
> > The new layout of the repository is the following:
> > - trunk/: contains the version under development (formerly known as
> dynare_v4/)
> > - branches/: containes the 3.x and 4.0 stable branches
> > - tags/: contains official dynare releases
> >
> > You have to download a fresh working copy of the repository (for several
> technical reasons it is impossible to convert your already existing
working
> copies; sorry for the inconvenience).
> > With command-line subversion, you should issue the following command:
> >
> > svn checkout https://www.dynare.org/svn/dynare
> >
> >
> > Please also note that Dynare++ is now in a separate repository, at
> address:
> >
> > https://www.dynare.org/svn/dynare++
> >
> > The same remarks apply.
> >
> > Ondra: you can contact me if you want me to setup mail announcements for
> each changeset, as for the Dynare repository. Please also feel free to
> reorganize the layout of the Dynare++ repository, since for the moment it
> only contains a single dynare++ subdirectory.
> >
> >
> > For the moment there is only a very rough web SVN browser, accessible at
> the same address than the repositories (type
> https://www.dynare.org/svn/dynare in your web browser). I will try to
setup
> a more friendly web browser soon.
> >
> > All the best
> >
> > Sébastien
> >
> >
> >
> > _______________________________________________
> > Dev mailing list
> > Dev(a)dynare.org
> > http://www.dynare.org/cgi-bin/mailman/listinfo/dev
> >
> >
>
Dear Michel
I did and it is both the new site,
https://www.dynare.org/svn/dynare
and the trunk subdirectory that I have been trying to download from:
https://www.dynare.org/svn/dynare/trunk
but I still have no luck and I am repeatedly getting same error messages:
Error: REPORT request failed on '/svn/dynare/!svn/vcc/default'
Error: Can't find a temporary directory: Internal error
Best regards
George
Mob. +44(0)7951415480
artilogica(a)btconnect.com
----- Original Message -----
From: "Michel Juillard" <michel.juillard(a)ens.fr>
To: "George Perendia" <artilogica(a)btconnect.com>; "G. Perendia"
<george(a)perendia.orangehome.co.uk>
Sent: Sunday, December 21, 2008 1:35 PM
Subject: [Fwd: [DynareDev] Dynare subversion server: migration complete]
>
> Hi George,
>
> you should have received this message via the Dynare developers email
list.
>
> Best
>
> Michel
>
> -------- Original Message --------
> Subject: [DynareDev] Dynare subversion server: migration complete
> Date: Fri, 19 Dec 2008 18:04:54 +0100
> From: Sébastien Villemot <sebastien.villemot(a)ens.fr>
> Reply-To: List for Dynare developers <dev(a)dynare.org>
> To: Tommaso Mancini <tommaso.mancini(a)stanfordalumni.org>,
> marco.ratto(a)jrc.it, Junior Maih <junior.maih(a)gmail.com>, Heesun Kiem
> <HKiem(a)imf.org>, Gianni Lombardo <giovanni.lombardo(a)ecb.int>,
> dev(a)dynare.org, Ondra Kamenik <ondra.kamenik(a)gmail.com>, Assia Ezzeroug
> <Assia.Ezzeroug(a)ens.fr>, Gary.Anderson(a)frb.gov
>
>
>
> Hi everybody,
>
> The migration of the Dynare subversion server is complete.
>
> Dynare subversion is now accessible at:
>
> https://www.dynare.org/svn/dynare
>
> We migrated the server to a secure connection (it is HTTPS and not HTTP
!!); there should be no security warning, since we have bought an official
digital certificate from Comodo.
>
> For committing changes, the user accounts and passwords are unchanged;
however, for increased security, we should change every individual password
in the future. We will do this in due time, when we find a way to securely
exchange passwords.
>
> The new layout of the repository is the following:
> - trunk/: contains the version under development (formerly known as
dynare_v4/)
> - branches/: containes the 3.x and 4.0 stable branches
> - tags/: contains official dynare releases
>
> You have to download a fresh working copy of the repository (for several
technical reasons it is impossible to convert your already existing working
copies; sorry for the inconvenience).
> With command-line subversion, you should issue the following command:
>
> svn checkout https://www.dynare.org/svn/dynare
>
>
> Please also note that Dynare++ is now in a separate repository, at
address:
>
> https://www.dynare.org/svn/dynare++
>
> The same remarks apply.
>
> Ondra: you can contact me if you want me to setup mail announcements for
each changeset, as for the Dynare repository. Please also feel free to
reorganize the layout of the Dynare++ repository, since for the moment it
only contains a single dynare++ subdirectory.
>
>
> For the moment there is only a very rough web SVN browser, accessible at
the same address than the repositories (type
https://www.dynare.org/svn/dynare in your web browser). I will try to setup
a more friendly web browser soon.
>
> All the best
>
> Sébastien
>
>
>
> _______________________________________________
> Dev mailing list
> Dev(a)dynare.org
> http://www.dynare.org/cgi-bin/mailman/listinfo/dev
>
>
Two last remarks:
- in normal times, you should only commit changes to the "trunk/" directory. No change should ever be made to the "tags/" subdirectory, which contains historical versions of Dynare. Changes to the "branches/" directories should only be bugfixes for inclusion in the future stable release.
- the subversion no longer contains any binary. This means that you must recompile the preprocessor and the Matlab DLLs by yourself. Some help can be found on:
http://www.dynare.org/DynareWiki/BuildingPreprocessorhttp://www.dynare.org/DynareWiki/BuildingDlls
Merry Christmas and happy new year to all of you
Sébastien
Hi everybody,
Today we are changing the location of Dynare subversion server.
Please no longer use http://www.cepremap.cnrs.fr/svn/ as the source
address for Dynare subversion.
I will send you the new address once it is set up, normally in a few
hours.
Sorry for informing you at the very last moment, we had initially not
planned to do the move so quickly.
All the best
Sébastien
Hi all,
I realize that I can't do myself the job of synchronizing the trunk
and the 4.0 branch of Dynare. I don't have enough knowledge of some
parts of the code to be able to decide whether to merge in the 4.0 the
changes made to the trunk.
I now think that the right solution is that the person who fixes a bug
in the trunk is responsible for fixing it in the 4.0 branch (provided
it also appears there, of course).
Since the release of Dynare 4.0.2 (SVN revision 2224), there have been
several changesets which fixed bugs (in the smoother, in OSR, in
mult_elimination...). I prefer to leave you the work of merging the
relevant ones in the 4.0 branch.
The idea is to merge only bug fixes, but not new features or code
restructuring (which could create new bugs), so that we can reasonably
think that the number of bugs is stricly decreasing in the 4.0.x series.
There are basically two ways of merging a changeset:
- if the 4.0 branch and the trunk code don't differ much in the
modified zones, you can use the "svn merge" command.
For example, if changeset 3456 contains bugfixes in the trunk that you
want to merge, go to "branches/4.0" directory, and type:
svn merge -c 3456 http://www.cepremap.cnrs.fr/svn/dynare_v4
This will apply the changeset to your local copy of the 4.0 branch. If
everything goes well, you can now commit it. If there is a conflict
you need to resolve it by hand. Note that it is possible to give
several changesets to the -c option, such as "-c 3456,4567,5678"
- otherwise, if the two codes differ two much, just fix the code "by
hand" in the 4.0 branch and commit
In the changelog message, please indicate the number of the changeset
that your merged, and a short description of what it did.
Cheers
Sébastien