Problems with setting up a personal code file
Stephen Read
So I have a student who is trying to set up a personal code file for working with emergent/leabra. About a week or two ago she successfully installed emergent/leabra, including successfully running ra25. But yesterday she tried to build her own code file this time when she tried to build and run ra25, she got messages saying something like Looper.Manager and Looper.NewManager had not been defined. This is using exactly the same ra25 file that she used to install leabra. I gather from looking at Github that were some changes made to the looper code and to the versions of leabra (and maybe emergent) which might be responsible for the problem. So my question is what go.mod file and version numbers should currently be used?
Steve
Stephen J. Read
Mendel B. Silberberg Professor of Social Psychology
Department of Psychology
University of Southern California
Los Angeles, CA 90089-1061
Website: www.stephenjread.com
Stephen Read
Here is a copy of the error message.
Randall O'Reilly
If this student did not update their go.mod file, it should still have been building against the older version and should have worked fine. In general, go.mod is highly reliable and ensures consistent building *as long as you leave it alone!*.
To update to the new version of looper, the latest module numbers are always available in the comp cog neuro sims go.mod:
cogentcore.org/core v0.3.5
github.com/emer/emergent/v2 v2.0.0-dev0.1.7
github.com/emer/leabra/v2 v2.0.0-dev0.5.5
github.com/emer/vision/v2 v2.0.0-dev0.1.0
The changes needed to update the ra25.go file to the new looper code are in this commit: https://github.com/emer/leabra/commit/0b1015d9cf1d126b75fe23f507c4b2678034a790
- Randy
> On Nov 8, 2024, at 1:02 PM, Stephen Read <re...@usc.edu> wrote:
>
> Here is a copy of the error message.
> You received this message because you are subscribed to the Google Groups "emergent-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to emergent-user...@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/emergent-users/BYAPR07MB46793620938D75FC238A6F84D75D2%40BYAPR07MB4679.namprd07.prod.outlook.com.
Stephen Read
Hi Randy,
Thanks for the response. We did finally figure out that she had the updated go.mod file, when she created her new directory, but she was using the ra25 file from when she initially installed emergent a week or two ago. Once she downloaded the latest version of ra25 everything went smoothly.
Thanks for pointing out that the latest module numbers can always be found in the comp cog neuro sims go.mod. That’s helpful. I had to search around when I updated my version of ra25.
Best, Steve
Stephen J. Read
Mendel B. Silberberg Professor of Social Psychology
Department of Psychology
University of Southern California
Los Angeles, CA 90089-1061
Website: www.stephenjread.com
From:
Randall O'Reilly <rcore...@gmail.com>
Date: Monday, November 11, 2024 at 10:24 AM
To: Stephen Read <re...@usc.edu>
Cc: emergen...@googlegroups.com <emergen...@googlegroups.com>
Subject: Re: Problems with setting up a personal code file
The issue here is that the looper code was updated, along with the new GUI, as I emailed about recently, though I might not have mentioned it here on the emergent users list. If this student did not update their go. mod file, it should still
The issue here is that the looper code was updated, along with the new GUI, as I emailed about recently, though I might not have mentioned it here on the emergent users list.
If this student did not update their go.mod file, it should still have been building against the older version and should have worked fine. In general, go.mod is highly reliable and ensures consistent building *as long as you leave it alone!*.
To update to the new version of looper, the latest module numbers are always available in the comp cog neuro sims go.mod:
cogentcore.org/core v0.3.5
github.com/emer/emergent/v2 v2.0.0-dev0.1.7
github.com/emer/leabra/v2 v2.0.0-dev0.5.5
github.com/emer/vision/v2 v2.0.0-dev0.1.0
The changes needed to update the ra25.go file to the new looper code are in this commit: https://urldefense.com/v3/__https://github.com/emer/leabra/commit/0b1015d9cf1d126b75fe23f507c4b2678034a790__;!!LIr3w8kk_Xxm!owTf-DO0WnUJzOvy4Ckd_v1bYcWFWxyqDqdwxcKxq1FiJaabKvao_YQVp2QcNdxFFupxFX_c7Ro7JYQ$
- Randy
> On Nov 8, 2024, at 1:02 PM, Stephen Read <re...@usc.edu> wrote:
>
> Here is a copy of the error message.
> <image001.png> Stephen J. Read
> Mendel B. Silberberg Professor of Social Psychology
> Department of Psychology
> University of Southern California
> Los Angeles, CA 90089-1061
> So I have a student who is trying to set up a personal code file for working with emergent/leabra. About a week or two ago she successfully installed emergent/leabra, including successfully running ra25. But yesterday she tried to build her own code file this time when she tried to build and run ra25, she got messages saying something like Looper.Manager and Looper.NewManager had not been defined. This is using exactly the same ra25 file that she used to install leabra. I gather from looking at Github that were some changes made to the looper code and to the versions of leabra (and maybe emergent) which might be responsible for the problem. So my question is what go.mod file and version numbers should currently be used?
> Steve
> Stephen J. Read
> Mendel B. Silberberg Professor of Social Psychology
> Department of Psychology
> University of Southern California
> Los Angeles, CA 90089-1061
>
> --
> You received this message because you are subscribed to the Google Groups "emergent-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to emergent-user...@googlegroups.com.