infomap-nlp-users

[infomap-nlp-users] still print_doc problems ...

[German R. <ri...@ls...>]

Dear all,

I'm using infomap-nlp-0.8.4 and I also have the print_doc problems when
retrieving documents.

[rigau@meaning infomap-nlp-0.8.4]$ associate -t -c kjbible god
god:1.000000
lord:0.670154
disgrace:0.617541
scoffers:0.567710
deceivableness:0.553055
...

[rigau@meaning infomap-nlp-0.8.4]$ associate -d -c kjbible god
3999484:0.800569
4300759:0.799777
4175212:0.796587
4179848:0.795709
...

Everything seems to be in place. However, print_doc don't find the models:

[rigau@meaning infomap-nlp-0.8.4]$ print_doc -c kjbible 3999484
model_params.c: read_model_params: can't stat model params file: No such 
file or directory
Can't read model params file "(null)/model_params.bin"

[rigau@meaning infomap-nlp-0.8.4]$ print_doc -m 
/home/rigau/tools/infomap-nlp-0.8.4/models -c kjbible 3999484
model_params.c: read_model_params: can't stat model params file: No such 
file or directory
Can't read model params file "(null)/model_params.bin"

Any suggestion? Thanks in advance,

German

Re: [infomap-nlp-users] still print_doc problems ...

[Dominic W. <dwi...@cs...>]

Dear German,

This seems to have been a pathnames problem: adding the line

 model_data_dir = strcat( model_dir_parent, model_tag );

seems to have fixed it (and another ++argv; --argc; has prevented the
printing of trivial files at the beginning of the results.

I've released a version 0.8.5 with these fixes - please let me know if
this solves it for you.

Best wishes,
Dominic

On Fri, 23 Apr 2004, German Rigau wrote:

>
> Dear all,
>
> I'm using infomap-nlp-0.8.4 and I also have the print_doc problems when
> retrieving documents.
>
> [rigau@meaning infomap-nlp-0.8.4]$ associate -t -c kjbible god
> god:1.000000
> lord:0.670154
> disgrace:0.617541
> scoffers:0.567710
> deceivableness:0.553055
> ...
>
> [rigau@meaning infomap-nlp-0.8.4]$ associate -d -c kjbible god
> 3999484:0.800569
> 4300759:0.799777
> 4175212:0.796587
> 4179848:0.795709
> ...
>
> Everything seems to be in place. However, print_doc don't find the models:
>
> [rigau@meaning infomap-nlp-0.8.4]$ print_doc -c kjbible 3999484
> model_params.c: read_model_params: can't stat model params file: No such
> file or directory
> Can't read model params file "(null)/model_params.bin"
>
> [rigau@meaning infomap-nlp-0.8.4]$ print_doc -m
> /home/rigau/tools/infomap-nlp-0.8.4/models -c kjbible 3999484
> model_params.c: read_model_params: can't stat model params file: No such
> file or directory
> Can't read model params file "(null)/model_params.bin"
>
> Any suggestion? Thanks in advance,
>
> German
>
>
>
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
> For a limited time only, get FREE Ground shipping on all orders of $35
> or more. Hurry up and shop folks, this offer expires April 30th!
> http://www.thinkgeek.com/freeshipping/?cpg=12297
> _______________________________________________
> infomap-nlp-users mailing list
> inf...@li...
> https://lists.sourceforge.net/lists/listinfo/infomap-nlp-users
>

Re: [infomap-nlp-users] still print_doc problems ...

[German R. <ri...@ls...>]

Dominic Widdows wrote:

>Dear German,
>
>This seems to have been a pathnames problem: adding the line
>
> model_data_dir = strcat( model_dir_parent, model_tag );
>
>seems to have fixed it (and another ++argv; --argc; has prevented the
>printing of trivial files at the beginning of the results.
>
>I've released a version 0.8.5 with these fixes - please let me know if
>this solves it for you.
>  
>

Dear Dominic,

Thanks a lot, however, it seems that the new version still not solve the 
problem.

[rigau@meaning infomap-nlp-0.8.5]$ associate -c kjbible god
god:1.000000
lord:0.670154
disgrace:0.617541
scoffers:0.567710
deceivableness:0.553055
...

[rigau@meaning infomap-nlp-0.8.5]$ associate -d -c kjbible god
3999484:0.800569
4300759:0.799777
4175212:0.796587
4179848:0.795709
2290800:0.795502
...

but

[rigau@meaning infomap-nlp-0.8.5]$ print_doc -c kjbible 3999484
model_params.c: read_corpus_format(): can't open file: No such file or 
directory
Can't read corpus format file 
"/home/rigau/tools/infomap-nlp-0.8.5/models/kibib/corpus_format.bin"

when nothing has been said about a "kibib" model. It do not exists at 
all. There is only
the kjbible in the models folder. Obviously, it is a path problem... or 
maybe I'm doing
something wrong...

Best wishes,

German

Re: [infomap-nlp-users] still print_doc problems ...

[Beate D. <do...@IM...>]

Dear German,

There was a bug in the commandline processing of print_doc. I just
committed a new version to the CVS repository. Let me know if you still
have difficulties running print_doc. We'll soon post a new official
release with the fixes, too.

Best wishes,
Beate



>Dear Dominic,
>
>Thanks a lot, however, it seems that the new version still not solve the
>problem.
>
>[rigau@meaning infomap-nlp-0.8.5]$ associate -c kjbible god
>god:1.000000
>lord:0.670154
>disgrace:0.617541
>scoffers:0.567710
>deceivableness:0.553055
>...
>
>[rigau@meaning infomap-nlp-0.8.5]$ associate -d -c kjbible god
>3999484:0.800569
>4300759:0.799777
>4175212:0.796587
>4179848:0.795709
>2290800:0.795502
>...
>
>but
>
>[rigau@meaning infomap-nlp-0.8.5]$ print_doc -c kjbible 3999484
>model_params.c: read_corpus_format(): can't open file: No such file or
>directory
>Can't read corpus format file
>"/home/rigau/tools/infomap-nlp-0.8.5/models/kibib/corpus_format.bin"
>
>when nothing has been said about a "kibib" model. It do not exists at
>all. There is only
>the kjbible in the models folder. Obviously, it is a path problem... or
>maybe I'm doing
>something wrong...
>
>Best wishes,
>
>German
>
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
>For a limited time only, get FREE Ground shipping on all orders of $35
>or more. Hurry up and shop folks, this offer expires April 30th!
>http://www.thinkgeek.com/freeshipping/?cpg=12297
>_______________________________________________
>infomap-nlp-users mailing list
>inf...@li...
>https://lists.sourceforge.net/lists/listinfo/infomap-nlp-users
>

[infomap-nlp-users] Releasing new verions: how to get around

[Dominic W. <dwi...@cs...>]

Dear All,

In reponse to a problem Beate had earlier with making new releases.

The cvs tag, autoconf, automake, make dist process that's supposed to
generate new distibutions automatically from the cvs information didn't
work for me either.

Instead I've started with the 2nd step of the process, chaning the
configure file (in the base directory) so that the version tags are up to
date. (I did this manually just editing configure in emacs and replacing
0.8.3 with 0.8.4, 0.8.4 with 0.8.5, etc.)

Running "configure" and then "make dist" from here produces the correct
tarball.

You can then navigate through the tortuous sourceforge documentation from
the project admin page, got to "File Releases", upload the new tarball via
anaonymous ftp to "upload.sourceforge.net" (remember to set the type to
"bin", I uploaded garbage the first time I tried yesterday!), fill in the
release notes forms, hope that doing these steps in a different order
doesn't erase the notes you've already typed in, and hope for the best.

If anyone who is more SourceForge savvy can give me tips to make this
process better(I'm still not sure I'm doing things right), pleae chime in.

Best wishes,
Dominic

[infomap-nlp-users] Spam apology re. Generating new Releases

[Dominic W. <dwi...@cs...>]

My apologies, the previous message was meant to go to the developers list
not the users list. Sorry for cluttering everybody's inbox: however, if
you *do* have a better idea of how to get releases automatically generated
from cvs and successfully uploaded to SourceForge, please write to me!

(and cc. inf...@li...)

-Dominic

On Fri, 23 Apr 2004, Dominic Widdows wrote:

>
> Dear All,
>
> In reponse to a problem Beate had earlier with making new releases.
>
> The cvs tag, autoconf, automake, make dist process that's supposed to
> generate new distibutions automatically from the cvs information didn't
> work for me either.
>
> Instead I've started with the 2nd step of the process, chaning the
> configure file (in the base directory) so that the version tags are up to
> date. (I did this manually just editing configure in emacs and replacing
> 0.8.3 with 0.8.4, 0.8.4 with 0.8.5, etc.)
>
> Running "configure" and then "make dist" from here produces the correct
> tarball.
>
> You can then navigate through the tortuous sourceforge documentation from
> the project admin page, got to "File Releases", upload the new tarball via
> anaonymous ftp to "upload.sourceforge.net" (remember to set the type to
> "bin", I uploaded garbage the first time I tried yesterday!), fill in the
> release notes forms, hope that doing these steps in a different order
> doesn't erase the notes you've already typed in, and hope for the best.
>
> If anyone who is more SourceForge savvy can give me tips to make this
> process better(I'm still not sure I'm doing things right), pleae chime in.
>
> Best wishes,
> Dominic
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
> For a limited time only, get FREE Ground shipping on all orders of $35
> or more. Hurry up and shop folks, this offer expires April 30th!
> http://www.thinkgeek.com/freeshipping/?cpg=12297
> _______________________________________________
> infomap-nlp-users mailing list
> inf...@li...
> https://lists.sourceforge.net/lists/listinfo/infomap-nlp-users
>