-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Questions #4
Comments
Hi Lucas, I cannot promise that I have a ton of time, but I am happy to answer/discuss what I can. I am at amahabal at gmail. I suppose you have been using "perl Seqsee.pl". Instead, please try "perl util/Console.pl". This allows you to run Seqsee multiple times on one or more sequences sequentially. Hopefully this is what you were asking about. Please note that three additional modules were needed for this to work that were not shown in modeles_needed file in the top directory. I have modified that file now with three entries at the very bottom. Regarding sequence description: please say more (what sequence did you try, and what explanation did you get)? I have not touched this code in ten years :) Best, |
Thank you! The first part of your response was very helpful. I'll need to fix my local Perl distribution and then run some tests, and once that's done I can send you a more detailed question about sequence description. Just from memory though, sequence description was displaying "Sequence description not working/implemented" or something to that effect even for known or standard sequences (like 212 2 2 2 2 3 2 or 525354 and so on). I'll do some more tests and let you know. |
After fixing my lisp distribution, the Console.pl module runs fine and does most of what I wanted. I'm able to get the "blocks" of the sequence by clicking "start" several times. Does Seqsee ever output more description than just the way it thinks the input should be split up? For example, the sequence "1 6 1 7 1 8" gets split into the blocks "1 6", "1 7".. but Seqsee doesn't output more description than this. Is this working as intended? I've also noticed that Seqsee gets stuck in a (seemingly) infinite loop when given a sequence like the fibonacci numbers. I know there's no reason to expect it to recognize them, but I thought that this was interesting. Anyway, thanks for your help! I'm all set to run some automated tests with Seqsee. I'm thinking of jury-rigging a piece of software to click the GUI buttons and type things for me, though, since I have quite a bit of data I want to test it on. Best, Lucas |
Dr.Mahabal:
I'm a student researcher interested in this project. In the past, I've chatted with Alexandre Linhares, Harry Foundalis, and Eric Nichols about FARG-related things.
Anyway, I have a few questions for you, would you mind sharing your email with me?
My email is my full name (Lucas Saldyt), all lowercase, @gmail.com.
I'd like to discuss quite a few things, depending on how busy you are, but I have one important technical question:
How could I run Seqsee non-graphically on linux on a large set of integer sequences? (Is there already a non-graphical way to run Seqsee? Otherwise, which Perl files should I hack on?) Inputting sequences to the graphical version is fine, but I'd like to automate this (without automating the GUI clicks and entries).
Also, it seems the sequence description is "broken"? I was able to modify some of the code producing this message and get basic sequence description, but how could I get the full descriptions available in your dissertation?
Best,
Lucas
The text was updated successfully, but these errors were encountered: