You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(3) |
Dec
(3) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(8) |
Feb
(3) |
Mar
(9) |
Apr
(6) |
May
(13) |
Jun
(33) |
Jul
(11) |
Aug
(17) |
Sep
(31) |
Oct
(64) |
Nov
(19) |
Dec
(28) |
2003 |
Jan
(5) |
Feb
(4) |
Mar
(11) |
Apr
(11) |
May
(4) |
Jun
(15) |
Jul
(4) |
Aug
(16) |
Sep
(14) |
Oct
(1) |
Nov
(3) |
Dec
(1) |
2004 |
Jan
(8) |
Feb
(24) |
Mar
(16) |
Apr
(23) |
May
(11) |
Jun
(16) |
Jul
(15) |
Aug
(1) |
Sep
(9) |
Oct
(2) |
Nov
(20) |
Dec
(37) |
2005 |
Jan
(10) |
Feb
(1) |
Mar
|
Apr
(9) |
May
(8) |
Jun
(1) |
Jul
(6) |
Aug
(14) |
Sep
(3) |
Oct
(35) |
Nov
(10) |
Dec
(3) |
2006 |
Jan
(10) |
Feb
(11) |
Mar
(8) |
Apr
(6) |
May
(2) |
Jun
(2) |
Jul
(5) |
Aug
(6) |
Sep
(6) |
Oct
(10) |
Nov
(6) |
Dec
(2) |
2007 |
Jan
(26) |
Feb
(17) |
Mar
|
Apr
(6) |
May
(3) |
Jun
(4) |
Jul
(5) |
Aug
|
Sep
(8) |
Oct
(3) |
Nov
(16) |
Dec
(20) |
2008 |
Jan
(32) |
Feb
(4) |
Mar
(14) |
Apr
(7) |
May
(13) |
Jun
(13) |
Jul
(21) |
Aug
(8) |
Sep
(6) |
Oct
(7) |
Nov
(4) |
Dec
(7) |
2009 |
Jan
(49) |
Feb
(11) |
Mar
(12) |
Apr
(20) |
May
(7) |
Jun
(11) |
Jul
(12) |
Aug
(3) |
Sep
(5) |
Oct
(12) |
Nov
(36) |
Dec
(14) |
2010 |
Jan
(35) |
Feb
(27) |
Mar
(84) |
Apr
(32) |
May
(42) |
Jun
(25) |
Jul
(50) |
Aug
(30) |
Sep
(8) |
Oct
(30) |
Nov
(69) |
Dec
(140) |
2011 |
Jan
(16) |
Feb
(26) |
Mar
(33) |
Apr
(23) |
May
(6) |
Jun
(20) |
Jul
(45) |
Aug
(14) |
Sep
(4) |
Oct
(8) |
Nov
(5) |
Dec
(9) |
2012 |
Jan
(2) |
Feb
(5) |
Mar
(14) |
Apr
(11) |
May
(7) |
Jun
(37) |
Jul
(11) |
Aug
(9) |
Sep
(7) |
Oct
(6) |
Nov
(4) |
Dec
(6) |
2013 |
Jan
(52) |
Feb
(28) |
Mar
(21) |
Apr
(17) |
May
(7) |
Jun
(12) |
Jul
(5) |
Aug
(10) |
Sep
(29) |
Oct
(3) |
Nov
(30) |
Dec
(1) |
2014 |
Jan
(6) |
Feb
(3) |
Mar
(9) |
Apr
(6) |
May
(8) |
Jun
(11) |
Jul
(2) |
Aug
(1) |
Sep
(6) |
Oct
(2) |
Nov
|
Dec
(5) |
2015 |
Jan
(3) |
Feb
(9) |
Mar
(6) |
Apr
(4) |
May
(5) |
Jun
(1) |
Jul
(1) |
Aug
(1) |
Sep
|
Oct
(1) |
Nov
(3) |
Dec
(3) |
2016 |
Jan
|
Feb
(40) |
Mar
(6) |
Apr
|
May
(2) |
Jun
(2) |
Jul
(5) |
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2017 |
Jan
|
Feb
(4) |
Mar
(3) |
Apr
|
May
(2) |
Jun
|
Jul
(5) |
Aug
(1) |
Sep
(2) |
Oct
|
Nov
|
Dec
|
2018 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
(1) |
May
(2) |
Jun
(1) |
Jul
(2) |
Aug
(1) |
Sep
(2) |
Oct
|
Nov
|
Dec
|
2019 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(1) |
2020 |
Jan
(1) |
Feb
|
Mar
|
Apr
(4) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
(2) |
Dec
(1) |
2021 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
(1) |
Oct
(2) |
Nov
|
Dec
(1) |
2022 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
(1) |
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
(1) |
Nov
(1) |
Dec
(1) |
2023 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
2024 |
Jan
|
Feb
(1) |
Mar
(3) |
Apr
(1) |
May
(5) |
Jun
(4) |
Jul
(4) |
Aug
(2) |
Sep
(2) |
Oct
(1) |
Nov
(1) |
Dec
(1) |
2025 |
Jan
(1) |
Feb
(1) |
Mar
(1) |
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Frederick I. <fre...@ya...> - 2017-07-23 22:53:40
|
Hi, I know - why wold anyone want to do this but just for fun lets assume that irix is a nice new fancy os :) I have downloaded YAP6.2.2 and that didn't get anywhere as it just throws a SIGBUS and dies when it tries to execute ./yap -b .pl/init.py during the build process. So I thought I would backup to 5.1.3 and see if that played nicely. It does better (except problems compiling two functions in c_interface.c which require REGISTER_BACKUP_REGS else it throws undeclared BK_H ? errors and a problem with fenv.h requiring a __c99 declaration). Once past this things got a bit better, although it throws a permission_error in a few of the bootstrap). Then it gives a "YOP OOPs this is probably a yap problem" error. I do not have the machine at hand right now - but can post an exact error stack later. I am using gcc 4.7.2 and irix 6.5 (although I am probably the only person with access to this. I have compiled with the -g flag so I can at least debug and get a stack trace from there. Any thoughts on where I should look of pieces of codeI can check to try to help identify this? Any assistance much appreciated.. Cheers Freddy |
From: Gökhan S. <so...@it...> - 2017-07-14 12:49:43
|
Copying *process.pl <http://process.pl>* and *process.so* files from installed yap-6.2.2 did not work. I fixed the syntax errors in *pybips.c*, there were not many as I thought at the beginning. But building *with-python* did not solve my problem neither. Gökhan Solak 2017-07-13 17:18 GMT+03:00 Gökhan Solak <so...@it...>: > I have copied all *.pl, *.yap files and directories under git repo > *yap-6.3/library* into *usr/local/share/Yap. *After that CLPFD library > was available via *yap. *However, I noticed that another library I need, > *process* is not available. It doesn't exist under yap-6.3 repo. Would > copying the process.pl file from yap-6.2.2 work? Is it replaced with > another library with similar capabilities? > > > Gökhan Solak > > 2017-07-12 22:18 GMT+03:00 Gökhan Solak <so...@it...>: > >> Forgot to mention my tools: >> >>> gcc (Ubuntu 4.8.5-2ubuntu1~14.04.1) 4.8.5 >>> >> GNU Make 3.81 >> >> >> >> Gökhan Solak >> >> 2017-07-12 22:14 GMT+03:00 Gökhan Solak <so...@it...>: >> >>> Hello, >>> >>> Short: >>> I have built Yap-6.3 from the latest source code. I can't locate or use >>> CLPFD library. It is not under *usr/local/share/Yap*. >>> >>> Long: >>> I have cloned the latest version of Yap-6.3 and built with the following >>> commands: >>> >>> mkdir build >>> >>> cd build >>> >>> ../configure --enable-coroutining=yes --with-gmp=/usr/lib/x86_64-linux-gnu >>> --enable-max-performance=yes >>> >>> make >>> >>> sudo make install >>> >>> At first, it gave lots of syntax errors at the *pybips.c* file, so I >>> removed *Py4Yap* from MakeFile and set WITH_PYTHON option to OFF in >>> CMakeLists.txt. >>> >>> After these changes I was able to build it. However, it shows syntax >>> errors for CLPFD specific operators in my PL code and I can't locate it in >>> libraries. Though it's written in autoloader.yap file. >>> >>> Do I need to add/remove any flags to the build options to obtain CLPFD? >>> >>> Regards, >>> Gökhan Solak >>> >> >> > |
From: Gökhan S. <so...@it...> - 2017-07-13 14:19:30
|
I have copied all *.pl, *.yap files and directories under git repo *yap-6.3/library* into *usr/local/share/Yap. *After that CLPFD library was available via *yap. *However, I noticed that another library I need, *process* is not available. It doesn't exist under yap-6.3 repo. Would copying the process.pl file from yap-6.2.2 work? Is it replaced with another library with similar capabilities? Gökhan Solak Mobil:+905058688653 2017-07-12 22:18 GMT+03:00 Gökhan Solak <so...@it...>: > Forgot to mention my tools: > >> gcc (Ubuntu 4.8.5-2ubuntu1~14.04.1) 4.8.5 >> > GNU Make 3.81 > > > > Gökhan Solak > > 2017-07-12 22:14 GMT+03:00 Gökhan Solak <so...@it...>: > >> Hello, >> >> Short: >> I have built Yap-6.3 from the latest source code. I can't locate or use >> CLPFD library. It is not under *usr/local/share/Yap*. >> >> Long: >> I have cloned the latest version of Yap-6.3 and built with the following >> commands: >> >> mkdir build >> >> cd build >> >> ../configure --enable-coroutining=yes --with-gmp=/usr/lib/x86_64-linux-gnu >> --enable-max-performance=yes >> >> make >> >> sudo make install >> >> At first, it gave lots of syntax errors at the *pybips.c* file, so I >> removed *Py4Yap* from MakeFile and set WITH_PYTHON option to OFF in >> CMakeLists.txt. >> >> After these changes I was able to build it. However, it shows syntax >> errors for CLPFD specific operators in my PL code and I can't locate it in >> libraries. Though it's written in autoloader.yap file. >> >> Do I need to add/remove any flags to the build options to obtain CLPFD? >> >> Regards, >> Gökhan Solak >> > > |
From: Gökhan S. <so...@it...> - 2017-07-12 19:35:51
|
Hello, Short: I have built Yap-6.3 from the latest source code. I can't locate or use CLPFD library. It is not under *usr/local/share/Yap*. Long: I have cloned the latest version of Yap-6.3 and built with the following commands: mkdir build cd build ../configure --enable-coroutining=yes --with-gmp=/usr/lib/x86_64-linux-gnu --enable-max-performance=yes make sudo make install At first, it gave lots of syntax errors at the *pybips.c* file, so I removed *Py4Yap* from MakeFile and set WITH_PYTHON option to OFF in CMakeLists.txt. After these changes I was able to build it. However, it shows syntax errors for CLPFD specific operators in my PL code and I can't locate it in libraries. Though it's written in autoloader.yap file. Do I need to add/remove any flags to the build options to obtain CLPFD? Regards, Gökhan Solak |
From: Gökhan S. <so...@it...> - 2017-07-12 19:35:49
|
Forgot to mention my tools: > gcc (Ubuntu 4.8.5-2ubuntu1~14.04.1) 4.8.5 > GNU Make 3.81 Gökhan Solak 2017-07-12 22:14 GMT+03:00 Gökhan Solak <so...@it...>: > Hello, > > Short: > I have built Yap-6.3 from the latest source code. I can't locate or use > CLPFD library. It is not under *usr/local/share/Yap*. > > Long: > I have cloned the latest version of Yap-6.3 and built with the following > commands: > > mkdir build > > cd build > > ../configure --enable-coroutining=yes --with-gmp=/usr/lib/x86_64-linux-gnu > --enable-max-performance=yes > > make > > sudo make install > > At first, it gave lots of syntax errors at the *pybips.c* file, so I > removed *Py4Yap* from MakeFile and set WITH_PYTHON option to OFF in > CMakeLists.txt. > > After these changes I was able to build it. However, it shows syntax > errors for CLPFD specific operators in my PL code and I can't locate it in > libraries. Though it's written in autoloader.yap file. > > Do I need to add/remove any flags to the build options to obtain CLPFD? > > Regards, > Gökhan Solak > |
From: Fabrizio R. <fab...@un...> - 2017-05-18 07:22:18
|
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= AI*IA Outgoing Mobility Grants 2017 Call for research visits Deadline for applications: June 20th, 2017 https://sites.google.com/a/aixia.it/italiano/premi/outgoing-mobility =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To favour mobility of young researchers the Italian Association for Artificial Intelligence (AI*IA) issues the AI*IA Outgoing Mobility Grants for 2017. Applications are solicited for funding a research visit abroad of a PhD student enrolled at an Italian University. AI*IA will cover the travel costs and living expenses (up to 2,000 euros) of successful applicants. The funding will be provided as a reimburswement for the expenses incurred in the visit. After the visit, the awarded person should send the Association the receipts of her/his costs for which she/he would like to be refunded. The central aim of these long visits is to build a research bridge between researchers and to create a solid basis for long term collaborations. Moreover, the visit has to lead to a submission of an article on a joint research topics to the Intelligenza Artificiale journal ( http://www.iospress.nl/journal/intelligenza-artificiale/). Applications can be made by students enrolled full-time in a PhD programme at an Italian University. The applicant must be a member of the Association for 2017. If she/he is not a member for 2017 she/he must register before applying. Funding is available for 2 students. The visit should start between the 15th of July 2017 and the 30th of June 2018. Deadline for applications: June 20th, 2017 Notification of grants: July 4th, 2017 The information required in the application are: 1. name of the Italian PhD student who will go abroad; 2. name of the foreign researcher who will host the student; 3. name and address of the foreign Lab/Department and University; 4. a short (max 2 pages) resume/CV of the Italian student; 5. a short (max 2 pages) resume/CV of the foreign researcher; 6. a short (max 2 pages) description of the research that will be carried out during the visit; 7. a budget of the foreseen expenses; 8. declaration of the foreign host indicating that the hosting institution is willing to provide office space and access to lab facilities to conduct the research; 9. expected visit dates. The applications must be sent by email to out...@ai... The applications will be examined by a committee composed by members of the AI*IA Board of Directors. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= |
From: Fabrizio R. <fab...@un...> - 2017-05-18 07:10:27
|
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= AI*IA Incoming Mobility Grants 2017 Call for research visits Deadline for applications: June 20th, 2017 https://sites.google.com/a/aixia.it/italiano/premi/incoming-mobility =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To favour mobility of young researchers the Italian Association for Artificial Intelligence (AI*IA) issues the AIxIA Incoming Mobility Grants for 2017. Applications are solicited for funding a research visit of a PhD student enrolled at a foreign University to an Italian institution. AI*IA will cover the travel costs and living expenses (up to 2,000 euros) of successful applicants. The funding will be provided as a reimbursement for the expenses incurred in the visit. After the visit, the awarded person should send the Association the receipts of her/his costs for which she/he would like to be refunded. The central aim of these long visits is to build a research bridge between researchers and to create a solid basis for long term collaborations. Moreover, the visit has to lead to a submission of an article on a joint research topics to the Intelligenza Artificiale journal ( www.iospress.nl/journal/intelligenza-artificiale/). Eligibility for the visiting student is to be enrolled full-time in a PhD programme at a foreign University. Funding is available for 2 students. The visit should start between the 15th of July 2017 and the 30th of June 2018. Deadline for applications: June 20th, 2017 Notification of grants: July 4th, 2017 The information required in the application are: 1. name of the foreign PhD student who will be hosted; 2. name and address of the foreign Lab/Department and University; 3. name of the Italian researcher of the hosting institution. The Italian researcher must be a member of the Association for 2016. If she/he is not a member for 2016 she/he must register before applying. 4. a short (max 2 pages) resume/CV of the foreign student; 5. a short (max 2 pages) resume/CV of the Italian host; 6. a short (max 2 pages) description of the research that will be carried out during the visit 7. a budget of the foreseen expenses; 8. declaration of the Italian host indicating that the hosting institution is willing to provide office space and access to lab facilities to conduct the research; 9. expected visit dates. The applications must be sent by email to inc...@ai... The applications will be examined by a committee composed by members of the AI*IA Board of Directors. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= |
From: Gökhan S. <so...@it...> - 2017-03-27 17:11:27
|
My YAP was 64-bit. But compiling with libGMP solved the problem. Thank you for the help. Regards, Gökhan Solak 2017-03-27 12:16 GMT+03:00 Vitor Santos Costa <vs...@gm...>: > Hi Gokhan > > You probably are using a 32 bit version of YAP. Have you tried 64 bit > or compiling with libGMP? > Your bug seems to be caused by this. > > Best > > > Vitor > > On Mon, Mar 27, 2017 at 9:40 AM, Gökhan Solak <so...@it...> wrote: > > Hello, > > > > I want to run a python process from my prolog script (YAP-6.2.2) and read > > its output formatted as a list of integers, e.g. [1,2,3,4,5,6]. > > > > This is what I do: > > > > :- use_module(library(process)). > > > > :- process_create(path(python3), > > ['my_script.py'], > > [stdout(pipe(Out))]), > > read(Out, OutputList), > > close(Out). > > > > However, it fails at read/2 predicate with the error: > > > > PL_unify_term: PL_int64 not supported > > Exception ignored in: <_io.TextIOWrapper name='<stdout>' mode='w' > > encoding='UTF-8'> > > BrokenPipeError: [Errno 32] Broken pipe > > > > I am sure that I can run the process correctly because with [stdout(std)] > > parameter given to process_create the program outputs [1,2,3,4,5,6] as > > expected. > > > > Weird thing is that when I change the process to output some > constant_term > > it still gives the same PL_int64 error. Appending a dot to the process' > > output ([1,2,3,4,5,6].) doesn't solve the error. Using read_term/3 gives > the > > same error. > > > > How can I solve this problem? > > > > This question is also asked here. > > > > Thanks in advance, > > Gökhan Solak > > > > ------------------------------------------------------------ > ------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > _______________________________________________ > > Yap-users mailing list > > Yap...@li... > > https://lists.sourceforge.net/lists/listinfo/yap-users > > > |
From: Vitor S. C. <vs...@gm...> - 2017-03-27 09:16:18
|
Hi Gokhan You probably are using a 32 bit version of YAP. Have you tried 64 bit or compiling with libGMP? Your bug seems to be caused by this. Best Vitor On Mon, Mar 27, 2017 at 9:40 AM, Gökhan Solak <so...@it...> wrote: > Hello, > > I want to run a python process from my prolog script (YAP-6.2.2) and read > its output formatted as a list of integers, e.g. [1,2,3,4,5,6]. > > This is what I do: > > :- use_module(library(process)). > > :- process_create(path(python3), > ['my_script.py'], > [stdout(pipe(Out))]), > read(Out, OutputList), > close(Out). > > However, it fails at read/2 predicate with the error: > > PL_unify_term: PL_int64 not supported > Exception ignored in: <_io.TextIOWrapper name='<stdout>' mode='w' > encoding='UTF-8'> > BrokenPipeError: [Errno 32] Broken pipe > > I am sure that I can run the process correctly because with [stdout(std)] > parameter given to process_create the program outputs [1,2,3,4,5,6] as > expected. > > Weird thing is that when I change the process to output some constant_term > it still gives the same PL_int64 error. Appending a dot to the process' > output ([1,2,3,4,5,6].) doesn't solve the error. Using read_term/3 gives the > same error. > > How can I solve this problem? > > This question is also asked here. > > Thanks in advance, > Gökhan Solak > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Yap-users mailing list > Yap...@li... > https://lists.sourceforge.net/lists/listinfo/yap-users > |
From: Gökhan S. <so...@it...> - 2017-03-27 09:03:23
|
Hello, I want to run a python process from my prolog script (YAP-6.2.2) and read its output formatted as a list of integers, e.g. [1,2,3,4,5,6]. This is what I do: :- use_module(library(process)). :- process_create(path(python3), ['my_script.py'], [stdout(pipe(Out))]), read(Out, OutputList), close(Out). However, it fails at read/2 predicate with the error: PL_unify_term: PL_int64 not supported Exception ignored in: <_io.TextIOWrapper name='<stdout>' mode='w' encoding='UTF-8'> BrokenPipeError: [Errno 32] Broken pipe I am sure that I can run the process correctly because with [stdout(std)] parameter given to process_create the program outputs [1,2,3,4,5,6] as expected. Weird thing is that when I change the process to output some constant_term it still gives the same PL_int64 error. Appending a dot to the process' output ([1,2,3,4,5,6].) doesn't solve the error. Using read_term/3 gives the same error. How can I solve this problem? This question is also asked here <http://stackoverflow.com/questions/43029488/read-a-list-from-stream-using-yap-prolog> . Thanks in advance, Gökhan Solak |
From: Petr P. <pp...@re...> - 2017-02-23 15:54:37
|
On Mon, Feb 13, 2017 at 02:53:07PM +0100, Petr Pisar wrote: > Hello, when building yap-6.2.2 with GCC 7, I obtain this build failure on i686 > only: > I tried 6.3.3 and it also fails on i686: LD_LIBRARY_PATH=/builddir/build/BUILDROOT/yap-6.3.3-1.fc26.i386/usr/lib:/builddir/build/BUILDROOT/yap-6.3.3-1.fc26.i386/usr/lib/Yap: YAPSHAREDIR=/builddir/build/BUILDROOT/yap-6.3.3-1.fc26.i386/usr/share/Yap YAPLIBDIR=/builddir/build/BUILDROOT/yap-6.3.3-1.fc26.i386/usr/lib/Yap /builddir/build/BUILDROOT/yap-6.3.3-1.fc26.i386/usr/bin/yap /builddir/build/BUILDROOT/yap-6.3.3-1.fc26.i386/usr/lib/Yap/startup.yss -q -f /builddir/build/BUILD/yap-6.3.3/packages/chr/chr_swi_bootstrap.pl \ -g "chr_compile_step2('/builddir/build/BUILD/yap-6.3.3/packages/chr/chr_translate_bootstrap2.chr','chr_translate_bootstrap2.pl'),halt" \ -t 'halt(1)' % reconsulting /builddir/build/BUILD/yap-6.3.3/packages/chr/chr_translate_bootstrap1.pl... % reconsulting /builddir/build/BUILD/yap-6.3.3/packages/chr/chr_runtime.pl... % reconsulting /builddir/build/BUILDROOT/yap-6.3.3-1.fc26.i386/usr/share/Yap/dialect/hprolog.yap... % reconsulting /builddir/build/BUILDROOT/yap-6.3.3-1.fc26.i386/usr/share/Yap/assoc.yap... % reconsulting /builddir/build/BUILDROOT/yap-6.3.3-1.fc26.i386/usr/share/Yap/rbtrees.yap... % reconsulted /builddir/build/BUILDROOT/yap-6.3.3-1.fc26.i386/usr/share/Yap/rbtrees.yap in module rbtrees, 10 msec 116424 bytes % reconsulted /builddir/build/BUILDROOT/yap-6.3.3-1.fc26.i386/usr/share/Yap/assoc.yap in module assoc, 11 msec 140032 bytes % reconsulted /builddir/build/BUILDROOT/yap-6.3.3-1.fc26.i386/usr/share/Yap/dialect/hprolog.yap in module hprolog, 14 msec 168392 bytes % including /builddir/build/BUILD/yap-6.3.3/packages/chr/chr_op.pl... % /builddir/build/BUILD/yap-6.3.3/packages/chr/chr_op.pl included in module chr_runtime, 0 msec 1152 bytes % Warning: (/builddir/build/BUILD/yap-6.3.3/packages/chr/chr_runtime.pl:378). % Discontiguous definition of chr_runtime:attr_unify_hook/2. % Warning: (/builddir/build/BUILD/yap-6.3.3/packages/chr/chr_runtime.pl:769). % Discontiguous definition of chr_runtime:exception/3. % reconsulted /builddir/build/BUILD/yap-6.3.3/packages/chr/chr_runtime.pl in module chr_runtime, 22 msec 252072 bytes % reconsulting /builddir/build/BUILDROOT/yap-6.3.3-1.fc26.i386/usr/share/Yap/ordsets.yap... % reconsulted /builddir/build/BUILDROOT/yap-6.3.3-1.fc26.i386/usr/share/Yap/ordsets.yap in module ordsets, 2 msec 32888 bytes % reconsulting /builddir/build/BUILD/yap-6.3.3/packages/chr/pairlist.pl... % reconsulted /builddir/build/BUILD/yap-6.3.3/packages/chr/pairlist.pl in module pairlist, 0 msec 6888 bytes % including /builddir/build/BUILD/yap-6.3.3/packages/chr/chr_op2.pl... % /builddir/build/BUILD/yap-6.3.3/packages/chr/chr_op2.pl included in module chr_translate_bootstrap1, 0 msec 904 bytes % reconsulted /builddir/build/BUILD/yap-6.3.3/packages/chr/chr_translate_bootstrap1.pl in module chr_translate_bootstrap1, 42 msec 674168 bytes % Translating CHR file chr_translate_bootstrap2.chr make[1]: *** [Makefile:43: chr_translate_bootstrap2.pl] Segmentation fault (core dumped) -- Petr |
From: Petr P. <pp...@re...> - 2017-02-13 15:42:19
|
On Mon, Feb 13, 2017 at 03:58:33PM +0100, Petr Pisar wrote: > Because i686 allows unaliagned access, I think a problem could be the signed > integer overflow in get_num() at C/scanner.c:567: > Even though this is a bug, it does not seem to be the cause of the access to illegal address. Building with -fwrapv experiences the same access to illegal address. -- Petr |
From: Petr P. <pp...@re...> - 2017-02-13 14:58:42
|
On Mon, Feb 13, 2017 at 02:53:07PM +0100, Petr Pisar wrote: > Hello, when building yap-6.2.2 with GCC 7, I obtain this build failure on i686 > only: [...] > Do you have any idea what's wrong? I guess GCC 7 brought some new > optimizations that leads to misbehaving code. > After compiling the code with -fsanitize=undefined compiler option, I can see these warnings: C/scanner.c:567:17: runtime error: signed integer overflow: 268435453 * 16 cannot be represented in type 'int' H/Yatom.h:161:39: runtime error: member access within misaligned address 0x1005c299 for type 'struct FunctorEntry', which requires 4 byte alignment H/Yatom.h:161:39: runtime error: member access within misaligned address 0x10120631 for type 'struct FunctorEntry', which requires 4 byte alignment H/Yatom.h:161:39: runtime error: member access within misaligned address 0x10120631 for type 'struct FunctorEntry', which requires 4 byte alignment H/Yatom.h:161:39: runtime error: member access within misaligned address 0x10120631 for type 'struct FunctorEntry', which requires 4 byte alignment H/Yatom.h:161:39: runtime error: member access within misaligned address 0x10120631 for type 'struct FunctorEntry', which requires 4 byte alignment H/Yatom.h:161:39: runtime error: member access within misaligned address 0x10120631 for type 'struct FunctorEntry', which requires 4 byte alignment H/Yatom.h:161:39: runtime error: member access within misaligned address 0x10120631 for type 'struct FunctorEntry', which requires 4 byte alignment H/Yatom.h:161:39: runtime error: member access within misaligned address 0x10120631 for type 'struct FunctorEntry', which requires 4 byte alignment H/Yatom.h:161:39: runtime error: member access within misaligned address 0x10063889 for type 'struct FunctorEntry', which requires 4 byte alignment H/Yatom.h:161:39: runtime error: member access within misaligned address 0x10063889 for type 'struct FunctorEntry', which requires 4 byte alignment H/Yatom.h:161:39: runtime error: member access within misaligned address 0x10063889 for type 'struct FunctorEntry', which requires 4 byte alignment C/absmi.c:12286:4: runtime error: member access within misaligned address 0x101e6e52 for type 'struct yami', which requires 4 byte alignment Because i686 allows unaliagned access, I think a problem could be the signed integer overflow in get_num() at C/scanner.c:567: Int val = 0L; [...] } else if (ch == 'x' && base == 0) { might_be_float = FALSE; if (--max_size == 0) { Yap_ErrorMessage = "Number Too Long"; return TermNil; } *sp++ = ch; ch = Nxtch(inp_stream); while (my_isxdigit(ch, 'F', 'f')) { Int oval = val; int chval = (chtype(ch) == NU ? ch - '0' : (my_isupper(ch) ? ch - 'A' : ch - 'a') + 10); if (--max_size == 0) { Yap_ErrorMessage = "Number Too Long"; return TermNil; } *sp++ = ch; → val = val * 16 + chval; if (oval != (val-chval)/16) /* overflow */ has_overflow = TRUE; ch = Nxtch(inp_stream); } *chp = ch; } -- Petr |
From: Petr P. <pp...@re...> - 2017-02-13 13:53:18
|
Hello, when building yap-6.2.2 with GCC 7, I obtain this build failure on i686 only: make[1]: Entering directory '/builddir/build/BUILD/yap-6.2.2/packages/clib' mkdir -p /builddir/build/BUILDROOT/yap-6.2.2-19.fc26.i386/usr/lib/Yap for f in unix.so random.so socket.so cgi.so memfile.so files.so mime.so crypt.so time.so readutil.so streaminfo.so process.so sha4pl.so uri.so; do \ /usr/bin/install -c $f /builddir/build/BUILDROOT/yap-6.2.2-19.fc26.i386/usr/lib/Yap; \ done mkdir -p /builddir/build/BUILDROOT/yap-6.2.2-19.fc26.i386/usr/share/Yap for f in ./unix.pl ./random.pl ./socket.pl ./cgi.pl ./memfile.pl ./filesex.pl ./mime.pl ./crypt.pl ./time.pl ./streaminfo.pl ./process.pl ./prolog_server.pl ./sha.pl ./socket.pl ./uri.pl; do \ /usr/bin/install -c -m 644 $f /builddir/build/BUILDROOT/yap-6.2.2-19.fc26.i386/usr/share/Yap; \ done LD_LIBRARY_PATH=/builddir/build/BUILDROOT/yap-6.2.2-19.fc26.i386/usr/lib:/builddir/build/BUILDROOT/yap-6.2.2-19.fc26.i386/usr/lib/Yap: YAPSHAREDIR=/builddir/build/BUILDROOT/yap-6.2.2-19.fc26.i386/usr/share/Yap YAPLIBDIR=/builddir/build/BUILDROOT/yap-6.2.2-19.fc26.i386/usr/lib/Yap /builddir/build/BUILDROOT/yap-6.2.2-19.fc26.i386/usr/bin/yap /builddir/build/BUILDROOT/yap-6.2.2-19.fc26.i386/usr/lib/Yap/startup.yss -f none -g make -t halt % Restoring file /builddir/build/BUILDROOT/yap-6.2.2-19.fc26.i386/usr/lib/Yap/startup.yss YAP 6.2.2 (i686-linux): Sun Feb 12 05:55:49 UTC 2017 MYDDAS version MYDDAS-0.9.1 % % % YAP OOOPS: tried to access illegal address 0x2024448b!!!!. % % 1295KB of Code Space (0x10000000--0x10143db0) % % PC: prolog:$file_is_unchanged/3 at clause 1 % Continuation: prolog:$ensure_file_unchanged/3 at clause 1 % 512KB of Global Stack (0x103ea000--0x1046a25c) % 0KB of Local Stack (0x10515d00--0x10516000) % 0KB of Trail (0x10516004--0x10516030) % Performed 0 garbage collections % All Active Calls and % Goals With Alternatives Open (Global In Use--Local In Use) % % prolog:$ensure_file_unchanged/3 at clause 1 % prolog:$ensure_file_unchanged/3 at clause 1 % prolog:$start_lf/11 at clause 2 % prolog:$lf/14 at clause 7 % prolog:$load_files/3 at clause 1 % idb:$lf_loaded/0 (512KB--0KB) % prolog:make/0 at clause 1 % prolog:once/1 at clause 1 % prolog:$do_yes_no/2 at clause 2 % prolog:$yes_no/2 at clause 1 % prolog:$catch/3 (512KB--0KB) % prolog:$system_catch/4 at clause 1 % prolog:$startup_goals/0 at clause 2 % prolog:$init_system/0 at clause 1 % prolog:$live/0 at clause 1 % meta-call Exiting .... make[1]: Leaving directory '/builddir/build/BUILD/yap-6.2.2/packages/clib' make[1]: *** [Makefile:175: install] Error 1 Do you have any idea what's wrong? I guess GCC 7 brought some new optimizations that leads to misbehaving code. -- Petr |
From: Fabrizio R. <fab...@un...> - 2016-10-03 08:25:10
|
Dear all, I would like to announce a new version of the web application http://cplint.lamping.unife.it for reasoning with probabilistic logic programming. The new version now includes the possibility of defining continuous random variables and of conditioning on continuous evidence using likelihood weighting and particle filtering. Examples of use include: · Gaussian Process regression <http://cplint.lamping.unife.it/example/inference/gpr.pl> · Particle filtering <http://cplint.lamping.unife.it/example/inference/kalman_filter.pl> · Dirichlet Process (stick breaking) <http://cplint.lamping.unife.it/example/inference/dirichlet_process.pl> · Dirichlet Process (Chinese restaurant) <http://cplint.lamping.unife.it/example/inference/dp_chinese.pl> · Dirichlet Process mixture model <http://cplint.lamping.unife.it/example/inference/dp_mix.pl> · Gaussian mixture <http://cplint.lamping.unife.it/example/inference/gaussian_mixture.pl> · Kalman filter <http://cplint.lamping.unife.it/example/inference/kalman_filter.pl> · Bayesian estimation <http://cplint.lamping.unife.it/example/inference/seven_scientists.pl> The application offers also facilities for plotting the distribution of sampled values. A tutorial is available at http://cplint.lamping.unife.it/tutorial/tutorial.swinb Please use the Google group cp...@go... ( https://groups.google.com/forum/#!forum/cplint) to send questions, suggestions, comments and bug reports. Best Fabrizio Riguzzi http://ds.ing.unife.it/~friguzzi/ |
From: Stefan K. <skr...@gm...> - 2016-07-29 15:57:57
|
Hi Andrew, a meta-interpreter is a good start. Which impure features do you use? Control flow stuff like cut and if-then-else? All-solution predicates like setof/3? Exceptions? Are you in control of the code that the meta-interpreter runs -- or is it contributed by some third party? Best Regards, Stefan. PS. So... how about moving the discussion to SO? On Jul 29, 2016 16:46, "Cropper, Andrew" <a.c...@im...> wrote: > Hi Stefan, > > I have replicated this by writing a meta-interpreter which keeps track of > the number of resolutions, which I will extend to include a resolution > limit. Although this solution works for my problem, it is not general > purpose because the meta-interpreter can only handle pure Prolog. > > Hope that helps a little, > > Andrew > > > > > > > > On 27 Jul 2016, at 21:08, Cropper, Andrew <a.c...@im...> > wrote: > > > > Hi Stefan, > > > > One option would be to replicate the SWI predicate in YAP, but this > seems a big job. I may be wrong but I think that YAP does not record the > number of inferences, so it would require a change there. > > > > We can move the discussion to StackOverflow. > > > > Kind regards, > > > > Andrew > > > > > > > > > > > > > > > >> On 27 Jul 2016, at 11:54, Stefan Kral <skr...@gm...> wrote: > >> > >> Hi Andrew, > >> > >> I'm looking for exactly the same feature too! > >> > >> Unlike you, I require a portable solution, as my primary Prolog > processor is SICStus Prolog—not YAP. That being said, let me emphasize that > I would love to see said feature in YAP, too, of course... what else?! > Right now, I cannot offer a working solution, but I can offer perspective: > >> > >> Let's move this discussion to StackOverflow! It addresses a much larger > audience and encourages cross-fertilization between different Prolog > processors (I hope). > >> > >> What are your thoughts on this? I'm looking to hearing from you soon! > >> > >> All the best, > >> Stefan. > >> > >> > >> On Jul 27, 2016 11:52, "Cropper, Andrew" <a.c...@im...> > wrote: > >> Hi all, > >> > >> I would like to enforce a limit on the number of inferences allowed to > find a solution for a given goal. This idea is akin to the > call_with_inference_limit(:Goal, +Limit, -Result) predicate in SWIPL. > >> > >> I have looked through the YAP documentation and there seems to be no > obvious way to do this. Has anyone tried to do this before, or know of a > relatively simple way to implement this? > >> > >> Thanks, > >> > >> Andrew > >> > ------------------------------------------------------------------------------ > >> What NetFlow Analyzer can do for you? Monitors network bandwidth and > traffic > >> patterns at an interface-level. Reveals which users, apps, and > protocols are > >> consuming the most bandwidth. Provides multi-vendor support for NetFlow, > >> J-Flow, sFlow and other flows. Make informed decisions using capacity > planning > >> reports.http://sdm.link/zohodev2dev > >> _______________________________________________ > >> Yap-users mailing list > >> Yap...@li... > >> https://lists.sourceforge.net/lists/listinfo/yap-users > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > > Yap-users mailing list > > Yap...@li... > > https://lists.sourceforge.net/lists/listinfo/yap-users > > |
From: Cropper, A. <a.c...@im...> - 2016-07-29 14:47:02
|
Hi Stefan, I have replicated this by writing a meta-interpreter which keeps track of the number of resolutions, which I will extend to include a resolution limit. Although this solution works for my problem, it is not general purpose because the meta-interpreter can only handle pure Prolog. Hope that helps a little, Andrew > On 27 Jul 2016, at 21:08, Cropper, Andrew <a.c...@im...> wrote: > > Hi Stefan, > > One option would be to replicate the SWI predicate in YAP, but this seems a big job. I may be wrong but I think that YAP does not record the number of inferences, so it would require a change there. > > We can move the discussion to StackOverflow. > > Kind regards, > > Andrew > > > > > > > >> On 27 Jul 2016, at 11:54, Stefan Kral <skr...@gm...> wrote: >> >> Hi Andrew, >> >> I'm looking for exactly the same feature too! >> >> Unlike you, I require a portable solution, as my primary Prolog processor is SICStus Prolog—not YAP. That being said, let me emphasize that I would love to see said feature in YAP, too, of course... what else?! Right now, I cannot offer a working solution, but I can offer perspective: >> >> Let's move this discussion to StackOverflow! It addresses a much larger audience and encourages cross-fertilization between different Prolog processors (I hope). >> >> What are your thoughts on this? I'm looking to hearing from you soon! >> >> All the best, >> Stefan. >> >> >> On Jul 27, 2016 11:52, "Cropper, Andrew" <a.c...@im...> wrote: >> Hi all, >> >> I would like to enforce a limit on the number of inferences allowed to find a solution for a given goal. This idea is akin to the call_with_inference_limit(:Goal, +Limit, -Result) predicate in SWIPL. >> >> I have looked through the YAP documentation and there seems to be no obvious way to do this. Has anyone tried to do this before, or know of a relatively simple way to implement this? >> >> Thanks, >> >> Andrew >> ------------------------------------------------------------------------------ >> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic >> patterns at an interface-level. Reveals which users, apps, and protocols are >> consuming the most bandwidth. Provides multi-vendor support for NetFlow, >> J-Flow, sFlow and other flows. Make informed decisions using capacity planning >> reports.http://sdm.link/zohodev2dev >> _______________________________________________ >> Yap-users mailing list >> Yap...@li... >> https://lists.sourceforge.net/lists/listinfo/yap-users > > ------------------------------------------------------------------------------ > _______________________________________________ > Yap-users mailing list > Yap...@li... > https://lists.sourceforge.net/lists/listinfo/yap-users |
From: Cropper, A. <a.c...@im...> - 2016-07-27 20:08:48
|
Hi Stefan, One option would be to replicate the SWI predicate in YAP, but this seems a big job. I may be wrong but I think that YAP does not record the number of inferences, so it would require a change there. We can move the discussion to StackOverflow. Kind regards, Andrew > On 27 Jul 2016, at 11:54, Stefan Kral <skr...@gm...> wrote: > > Hi Andrew, > > I'm looking for exactly the same feature too! > > Unlike you, I require a portable solution, as my primary Prolog processor is SICStus Prolog—not YAP. That being said, let me emphasize that I would love to see said feature in YAP, too, of course... what else?! Right now, I cannot offer a working solution, but I can offer perspective: > > Let's move this discussion to StackOverflow! It addresses a much larger audience and encourages cross-fertilization between different Prolog processors (I hope). > > What are your thoughts on this? I'm looking to hearing from you soon! > > All the best, > Stefan. > > > On Jul 27, 2016 11:52, "Cropper, Andrew" <a.c...@im...> wrote: > Hi all, > > I would like to enforce a limit on the number of inferences allowed to find a solution for a given goal. This idea is akin to the call_with_inference_limit(:Goal, +Limit, -Result) predicate in SWIPL. > > I have looked through the YAP documentation and there seems to be no obvious way to do this. Has anyone tried to do this before, or know of a relatively simple way to implement this? > > Thanks, > > Andrew > ------------------------------------------------------------------------------ > What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic > patterns at an interface-level. Reveals which users, apps, and protocols are > consuming the most bandwidth. Provides multi-vendor support for NetFlow, > J-Flow, sFlow and other flows. Make informed decisions using capacity planning > reports.http://sdm.link/zohodev2dev > _______________________________________________ > Yap-users mailing list > Yap...@li... > https://lists.sourceforge.net/lists/listinfo/yap-users |
From: Stefan K. <skr...@gm...> - 2016-07-27 10:54:36
|
Hi Andrew, I'm looking for exactly the same feature too! Unlike you, I require a portable solution, as my primary Prolog processor is SICStus Prolog—not YAP. That being said, let me emphasize that I would love to see said feature in YAP, too, of course... what else?! Right now, I cannot offer a working solution, but I can offer perspective: Let's move this discussion to StackOverflow! It addresses a much larger audience and encourages cross-fertilization between different Prolog processors (I hope). What are your thoughts on this? I'm looking to hearing from you soon! All the best, Stefan. On Jul 27, 2016 11:52, "Cropper, Andrew" <a.c...@im...> wrote: > Hi all, > > I would like to enforce a limit on the number of inferences allowed to > find a solution for a given goal. This idea is akin to the > call_with_inference_limit(:Goal, +Limit, -Result) predicate in SWIPL. > > I have looked through the YAP documentation and there seems to be no > obvious way to do this. Has anyone tried to do this before, or know of a > relatively simple way to implement this? > > Thanks, > > Andrew > > ------------------------------------------------------------------------------ > What NetFlow Analyzer can do for you? Monitors network bandwidth and > traffic > patterns at an interface-level. Reveals which users, apps, and protocols > are > consuming the most bandwidth. Provides multi-vendor support for NetFlow, > J-Flow, sFlow and other flows. Make informed decisions using capacity > planning > reports.http://sdm.link/zohodev2dev > _______________________________________________ > Yap-users mailing list > Yap...@li... > https://lists.sourceforge.net/lists/listinfo/yap-users > |
From: Cropper, A. <a.c...@im...> - 2016-07-27 09:52:23
|
Hi all, I would like to enforce a limit on the number of inferences allowed to find a solution for a given goal. This idea is akin to the call_with_inference_limit(:Goal, +Limit, -Result) predicate in SWIPL. I have looked through the YAP documentation and there seems to be no obvious way to do this. Has anyone tried to do this before, or know of a relatively simple way to implement this? Thanks, Andrew |
From: Fabrizio R. <fab...@un...> - 2016-06-01 06:12:32
|
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= AI*IA Outgoing Mobility Grants 2016 Call for research visits Deadline for applications: 10 June 2016 https://sites.google.com/a/aixia.it/italiano/premi/outgoing-mobility =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To favour mobility of young researchers the Italian Association for Artificial Intelligence (AI*IA) issues the Association Outgoing Mobility Grants for 2015. Applications are solicited for funding a research visit abroad of a PhD student enrolled at an Italian University. Students will be funded by AI*IA which will cover their travel costs and living expenses (up to 2000 euro). The funding will be provided as a reimbursement for the expenses incurred in the visit. After the visit, the awarded person should send the Association the receipts of her/his costs for which she/he would like to be refunded. The central aim of these extended visits is to build a research bridge between researchers and to create a solid basis for long term collaborations. Moreover, the visit has to lead to a submission of an article on a joint research topics to the Intelligenza Artificiale journal. Applications can be made by a student enrolled full-time in a PhD programme at an Italian University. The applicant must be a member of the Association for 2016. If she/he is not a member for 2016 she/he must register before applying. Funding is available for 2 students. The visit start should be between the 1st July 2016 and the 30th of June 2017. Deadline for applications: 10 June 2016 Notification of grants: 22 June 2016 The information required in the application are: 1. name of the Italian PhD student who will go abroad; 2. name of the foreign researcher that will host the student; 3. name and address of the foreign Lab/Department and University; 4. a short (max 2 pages) resume/CV of the Italian student; 5. a short (max 2 pages) resume/CV of the foreign researcher; 6. a short (max 2 pages) description of the research that will be carried out during the visit 7. a budget of the foreseen expenses 8. declaration of the foreign host indicating that the hosting institution is willing to provide office space and access to lab facilities to conduct the research 9. expected visit dates The application must be sent by email to out...@ai... The applications will be examined by a committee composed by members of the AI*IA Board of Directors. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= |
From: Fabrizio R. <fab...@un...> - 2016-06-01 06:11:07
|
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= AI*IA Incoming Mobility Grants 2016 Call for research visits Deadline for applications: 10 June 2016 https://sites.google.com/a/aixia.it/italiano/premi/incoming-mobility =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To favour mobility of young researchers the Italian Association for Artificial Intelligence (AI*IA) issues the Association Incoming Mobility Grants for 2015. Applications are solicited for funding a research visit of a PhD student enrolled at a foreign University to an Italian institution. Students will be funded by AI*IA which will cover their travel costs and living expenses (up to 2000 euro). The funding will be provided as a reimbursement for the expenses incurred in the visit. After the visit, the awarded person should send the Association the receipts of her/his costs for which she/he would like to be refunded. The central aim of these extended visits is to build a research bridge between researchers and to create a solid basis for long term collaborations. Moreover, the visit has to lead to a submission of an article on a joint research topics to the Intelligenza Artificiale journal. Eligibility for the visiting student is to be enrolled full-time in a PhD programme at a foreign University. Funding is available for 2 students. The visit start should be between the 1st July 2016 and the 30th of June 2017. Deadline for applications: 10 June 2016 Notification of grants: 22 June 2016 The information required in the application are: 1. name of the foreign PhD student who will be hosted; 2. name and address of the foreign Lab/Department and University; 3. name of the Italian researcher of the hosting institution. The Italian researcher must be a member of the Association for 2016. If she/he is not a member for 2016 she/he must register before applying. 4. a short (max 2 pages) resume/CV of the foreign student; 5. a short (max 2 pages) resume/CV of the Italian host; 6. a short (max 2 pages) description of the research that will be carried out during the visit 7. a budget of the foreseen expenses 8. declaration of the Italian host indicating that the hosting institution is willing to provide office space and access to lab facilities to conduct the research 9. expected visit dates The application must be sent by email to inc...@ai... The applications will be examined by a committee composed by members of the AI*IA Board of Directors. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= |
From: Fabrizio R. <fab...@un...> - 2016-05-06 15:17:44
|
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= AI*IA Outgoing Mobility Grants 2016 Call for research visits Deadline for applications: 10 June 2016 https://sites.google.com/a/aixia.it/italiano/premi/outgoing-mobility =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To favour mobility of young researchers the Italian Association for Artificial Intelligence (AI*IA) issues the Association Outgoing Mobility Grants for 2015. Applications are solicited for funding a research visit abroad of a PhD student enrolled at an Italian University. Students will be funded by AI*IA which will cover their travel costs and living expenses (up to 2000 euro). The funding will be provided as a reimbursement for the expenses incurred in the visit. After the visit, the awarded person should send the Association the receipts of her/his costs for which she/he would like to be refunded. The central aim of these extended visits is to build a research bridge between researchers and to create a solid basis for long term collaborations. Moreover, the visit has to lead to a submission of an article on a joint research topics to the Intelligenza Artificiale journal. Applications can be made by a student enrolled full-time in a PhD programme at an Italian University. The applicant must be a member of the Association for 2016. If she/he is not a member for 2016 she/he must register before applying. Funding is available for 2 students. The visit start should be between the 1st July 2016 and the 30th of June 2017. Deadline for applications: 10 June 2016 Notification of grants: 22 June 2016 The information required in the application are: 1. name of the Italian PhD student who will go abroad; 2. name of the foreign researcher that will host the student; 3. name and address of the foreign Lab/Department and University; 4. a short (max 2 pages) resume/CV of the Italian student; 5. a short (max 2 pages) resume/CV of the foreign researcher; 6. a short (max 2 pages) description of the research that will be carried out during the visit 7. a budget of the foreseen expenses 8. declaration of the foreign host indicating that the hosting institution is willing to provide office space and access to lab facilities to conduct the research 9. expected visit dates The application must be sent by email to out...@ai... The applications will be examined by a committee composed by members of the AI*IA Board of Directors. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= |
From: Fabrizio R. <fab...@un...> - 2016-05-06 15:16:08
|
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= AI*IA Incoming Mobility Grants 2016 Call for research visits Deadline for applications: 10 June 2016 https://sites.google.com/a/aixia.it/italiano/premi/incoming-mobility =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To favour mobility of young researchers the Italian Association for Artificial Intelligence (AI*IA) issues the Association Incoming Mobility Grants for 2015. Applications are solicited for funding a research visit of a PhD student enrolled at a foreign University to an Italian institution. Students will be funded by AI*IA which will cover their travel costs and living expenses (up to 2000 euro). The funding will be provided as a reimbursement for the expenses incurred in the visit. After the visit, the awarded person should send the Association the receipts of her/his costs for which she/he would like to be refunded. The central aim of these extended visits is to build a research bridge between researchers and to create a solid basis for long term collaborations. Moreover, the visit has to lead to a submission of an article on a joint research topics to the Intelligenza Artificiale journal. Eligibility for the visiting student is to be enrolled full-time in a PhD programme at a foreign University. Funding is available for 2 students. The visit start should be between the 1st July 2016 and the 30th of June 2017. Deadline for applications: 10 June 2016 Notification of grants: 22 June 2016 The information required in the application are: 1. name of the foreign PhD student who will be hosted; 2. name and address of the foreign Lab/Department and University; 3. name of the Italian researcher of the hosting institution. The Italian researcher must be a member of the Association for 2016. If she/he is not a member for 2016 she/he must register before applying. 4. a short (max 2 pages) resume/CV of the foreign student; 5. a short (max 2 pages) resume/CV of the Italian host; 6. a short (max 2 pages) description of the research that will be carried out during the visit 7. a budget of the foreseen expenses 8. declaration of the Italian host indicating that the hosting institution is willing to provide office space and access to lab facilities to conduct the research 9. expected visit dates The application must be sent by email to inc...@ai... The applications will be examined by a committee composed by members of the AI*IA Board of Directors. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= |
From: Douglas M. <log...@gm...> - 2016-03-20 11:57:23
|
On Wed, Mar 16, 2016 at 6:54 AM, Gökhan Solak <so...@it...> wrote: > Thank you for the answer. Using MSYS2 I was able to build yap 6.3.0 from > source, with some additional changes to source code. > > Changes I did were: > > In Regs.h, line 590, > > #define H Yap_REGS.H_ /* top of heap (global) > stack */ > > was causing compile error: > > error: expected ‘:’, ‘,’, ‘;’, ‘}’ or ‘__attribute__’ before ‘=’ token > > So I refactored *#define H* with *#define HEAD*. And I changed every > occurrence of *H *with *HEAD* in all *.c and *.h files under yap-source. > (Using Notepad++ replaced every ([^\d\w'])H([^\d\w']) with \1HEAD\2). > > In blob.c, compile error was caused: > > stderr undeclared (first use in this function) > > So I added #include <stdio.h> > > Now I am able to run it from yap.exe, it seems to work properly so far. > > Regards, > Gökhan Solak > Gokhan, Hey neat! I don't want to add too much work for you Gokhan.. but it would be helpful to at least me. Make an acct on Github (if you do not already have one)... and fork https://github.com/vscosta/yap-6.3 and make some changes in your repo you need.. (By forking .. I'll see where your repo is automatically) The reasoning (and I know this makes it harder): 1) You'll be on the bleeding edge of YAP (but relevant to any of the current work) 2) You'll either confirm (or hopefully disproved) a suspected bug in current (that I keep working around using a hybrid of old and new code rather than fixing) where the standard streams are not set up correctly (but also maybe yap-init.yss doesn't get built) 3) Your edits will be most helpfull to me! > > 2016-03-15 3:39 GMT+02:00 Vitor Santos Costa <vs...@gm...>: > >> Hi Gokhan >> >> Sorry for the delay. Thanks for your interest! >> >> I think the problem is that 6.4.0 is very old and cygwin has changed a >> lot. Quite a lot. >> >> Right now I still have some problems with the github YAP version on >> Windows. If you want to give it a try, probably wan to install first msys2: >> >> https://msys2.github.io/ >> >> That seems to have the best development environment. Thanks to cmake I >> was also able to compile YAP under VC and VisualStudio plus clang, but I >> haven't had the time to debug it so far. >> >> I have had problems with my version, but I am not sure where the problem >> comes from: YAP or WIndows 10. >> > Vitor, Hrrm you know, I wasn't using MSYS2 (just plain old Visual Studio C++) But if we end up using MSYS2, this works out for me since that is very usable from Visual C++ now. (Though it be sad to totally abandon Visual C++ but for now MSYS2 is nice ) Thanks in advance (both of you) Douglas Miles |