[IPOL discuss] testing the new version of the demos

[Juan Cardelino]

Ok. Here are my answers, I won't write interleaved because it would be a mess.

1) Network issue: I tried two different days, so it seemed more a typo
on the file name than a temporary network error. I tried again today
with the 22/11 version (6 days after the first try) and still
persists. Here is the line that fails.
[22/Nov/2010:15:53:54] SETUP/my_affine_sift building
[22/Nov/2010:15:53:54] BUILD retrieving:
http://www.ipol.im/pub/algo/my_affine_sift/ASIFT_png.tar.gz

2) about content management systems I have a considerable experience
with some wiki systems:
a)tikiwiki: the first one I tried: uses a mysql backend, is php based
and the syntax is reasonable, but apart from that, is as good as any
wiki. I think the media support is kind of limited.
b)twiki: very simple text file backend, cgi based, also nice syntax
but almost no media support
c)mediawiki (wikipedia engine): I think this is a great option: php
based, mysql frontend, enormous user based. supports various types of
media, latex formulae, gnuplot, graphivz, and code highlighting. and
many more extensions. The only downside I see is that it is not
intented for restricted access, so the user management and validation
system is not as good as it could be.

3) Another option is to go for a classic CMS, not only a wiki. In this
sense, I've been also playing quite a time with drupal: I think it is
a wonderful CMS to build large sites and to separate content from
style. On the other hand, I'm not sure about the inclusion of latex or
other technical stuff.
Summarizing, I would go for mediawiki or drupal, depending on the
requirementes. Maybe it could be worth to write down a short
specification of the capabilities we need for the CMS and then define
which system fullfils the requirements.

4) ccache dependency:  seems to be in the cm_fds_mcm_amss demo (still
fails on 22/11 version):
[22/Nov/2010:15:40:33] SETUP/cm_fds_mcm_amss building
[22/Nov/2010:15:40:33] BUILD retrieving:
http://www.ipol.im/pub/algo/cm_fds_mcm_amss/fds_mcm.tar.gz
[22/Nov/2010:15:40:34] BUILD retrieved
[22/Nov/2010:15:40:34] BUILD extracted:
/home/juanc/juanc/trabajo/ipol/ipol_demo/app/cm_fds_mcm_amss/dl/fds_mcm.tar.gz
[22/Nov/2010:15:40:34] BUILD running: make -C
/home/juanc/juanc/trabajo/ipol/ipol_demo/app/cm_fds_mcm_amss/src/fds_mcm/mcm
mcm CC='ccache cc' OMP=1 -j4


That's all for now.
Thanks for your time.

On Mon, Nov 22, 2010 at 10:50 AM, Nicolas Limare
<nicolas.limare at cmla.ens-cachan.fr> wrote:
>> I'm starting to re-implement my demo (which i've finished in
>> september) on the new version of the code. There area a few issues I'd
>> like to point out:
>
> Thanks for your feedback.
>
>> *I couldn't run the demo from ipol_demo_release-20101116.tar.gz at
>> first. After some hacking, I've discovered that the demo was not
>> built, because I've just ran ./demo.py. Although it is mentioned
>> indirectly, I think it should be explicitly said that you first need
>> to do a ./demo.py build before running ./demo.py, because the default
>> action is to run (without building) and the error you get is difficult
>> to read at first.
>
> OK, I corrected the README.txt file, it will be in the daily source
> code snapshot tonight.
> For your information, the "build" step is not automatically performed
> because any autoimatic reload (triggered by a file modified while the
> server is running) would imply a re-build, including re-download of
> the source codes.
>
>> *Finally, build failed for the cm_fds_mcm_amss demo, because I had a
>> timeout when downloading the code. This happened from two different
>> places and at two different times of the day, so I'm sure it is not my
>> problem.
>
> Maybe it was a temporary network problem. There has been some router
> reconfiguration on the ENS network lately.
>
>> *I've tried to correct a typo on the "Anatomy of an IPOL demo" but it
>> is locked. shall i pass you the location of the typo? As you said
>> "correct it yourself..."
>
> Until September, only jose-Luis and I needed to modify these pages,
> and as we are wiki admins there was no problem. But you should also
> be able to edit the demo documentation. So I just unlocked all the
> admin/demo pages.
>
> PS: The wiki system was good and usable when starting IPOL, but it's
> gradually showing its limits, particularly in handling the users and
> permissions. If some of you know about flexible content management
> systems (plone? django?), I'd like to heare your suggestions.
>
>> *do we still need to get the .tar.gz? or can we get the code from git?
>> if so, what is required (ssh access or whatsoever)?
>
> git requires ssh access, but is located on the demo server, and this
> server is not adapted to multiple user accounts. So for the moment, we
> are stuck to these tar.gz snapshots. But I heard today that the CMLA server
> room equipment will be installed this Thursday. We will start to
> install the new demo server immediately after, and I think that within
> one week we will have an development server (with ssh accounts and git
> repositories) on the current server.
>
>> *I still think that we could avoid using hard coded names for the
>> input images (input_0.png appears 4 times in the saxpb demo), can't we
>> have some strings named image_0, image_1 and so on. those should be
>> attributes of the app class. I'm not talking about a mandatory thing,
>> but maybe if we put it in some demos, people can use the idea.
>
> That's possible,. sure,  but I don't see the benefit of using
> self.input_0 instead of "input_0.png".
>
>> Some more issues:
>> *there is an untold dependency of ccache on one of the demos.
>
> The makefile for this demo is probably not correctly writen, it should
> only use ccache if it is available. Do you know which one it is?
>
>> *some code appears to be missing, when building my_affine_sift i get
>> the following error:
>
> Yes, I will solve this issue with the ASIFT author.
>
> --
> Nicolas LIMARE
> http://nicolas.limare.net/                         pgp:0xFA423F4F
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
>
> iEYEARECAAYFAkzqZwUACgkQvviFAPpCP08GoQCfWwmwblLBDVdCtDC0EKXEtEqQ
> /dIAoJjwmgN8Rdalk1TtgnIHSLC1K17m
> =l148
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> discuss mailing list
> discuss at list.ipol.im
> http://tools.ipol.im/mailman/listinfo/discuss
>