[00:07] *** Adityab left irc: Ping timeout: 240 seconds [01:12] *** Gamegoofs2 left irc: Ping timeout: 252 seconds [01:38] *** devon_hillard left irc: Read error: Connection reset by peer [02:02] *** Adityab joined #setiquest. [02:53] *** jrseti__ left irc: Ping timeout: 276 seconds [03:29] *** Adityab left irc: Ping timeout: 276 seconds [06:25] *** sigblips left irc: Quit: sigblips [08:34] *** Adityab joined #setiquest. [09:25] *** Adityab left irc: Read error: Connection reset by peer [09:40] *** devon_hillard joined #setiquest. [11:56] *** nbprashanth joined #setiquest. [11:58] *** nbprashanth left irc: Client Quit [13:16] *** akhand joined #setiquest. [13:21] *** akhand left irc: Ping timeout: 252 seconds [13:21] *** Adityab joined #setiquest. [13:45] *** khrm joined #setiquest. [13:58] *** khrm left irc: Ping timeout: 258 seconds [14:12] *** Adityab left irc: Ping timeout: 276 seconds [14:13] *** khrm joined #setiquest. [14:20] *** khrm left irc: Ping timeout: 276 seconds [14:38] *** khrm joined #setiquest. [15:21] *** khrm left irc: Ping timeout: 260 seconds [15:35] *** khrm joined #setiquest. [15:38] *** sigblips joined #setiquest. [16:13] *** akhand joined #setiquest. [16:20] *** Pjaya joined #setiquest. [16:21] *** Pjaya left #setiquest. [16:26] *** jrseti_ joined #setiquest. [16:54] *** khrm left irc: Ping timeout: 260 seconds [17:00] *** Pjaya joined #setiquest. [17:01] Hello all [17:01] Hello [17:02] I see Akhand, Pjaya, who else? [17:02] Gagan was going to be here [17:02] hello!! [17:03] I suppose gagan is not here [17:03] I've been working on http://setiquest.org/wiki/index.php/Telescope_Simulator_Architecture [17:03] i hope to have it completed just after the meeting. [17:04] After I complete this document we can all add to it or comment. [17:04] Ok can we just go through it [17:04] Following this will be a Detailed Design Document that we can all work on. I hope to have the first draft ready this afternoon. [17:05] Gamegoofs2 created a VERY simple eclipse project and I checked it into github [17:05] Ok [17:06] Has anyone reviewed the BackendServer code? [17:06] i started looking into it [17:06] http://setiquest.org/wiki/index.php/Telescope_Simulator_BackendServer [17:06] still couldnt understand much [17:06] Could not really do that due to my exams going on [17:07] but i looked through the code and would be able to get the commands out of it [17:07] Pjaya: yes! That is one of the big problems with it! Hard to understand. So we need to make it easier to understand. [17:07] Akhand - no problem, exams will be over soon enough [17:08] This afternoon I'll post the first draft of the detailed design document and so that will be the place we will document the commands [17:08] jrseti: sure i am hoping for that too :) [17:08] *** khrm joined #setiquest. [17:08] great [17:09] I added all of you to the project at http://issues.setiquest.org/projects/telescope-simulator [17:10] Ok But we need to synchronize our efforts on that [17:10] i mean work should not be redundant.. [17:11] but need to have a rough understanding of the big picture [17:11] yes, the issues.setiquest.org is meant to help us synchronize. Also, I hope all have the "watch" option selected on http://setiquest.org/wiki/index.php/Talk:Telescope_Simulator [17:11] hope the Architecture design ll help [17:12] The big picture should come from the Architecture document I'll have ready shortly after this IRC chat. [17:12] We all need to work together to make sure it makes sense and is complete enough to "get the big picture" [17:12] yeah sure Jrseti that would be a great help [17:13] If it does not make total sense, we will all need to fix it up [17:14] yape. [17:14] I am a bit overwhelmed with all of this, so please be patient and ask questions when you need to. [17:15] yeah sure i understand working on too many things can be hectic [17:16] I think the most important task from our side would be to document the commands at this time [17:16] Is that the http://setiquest.org/wiki/index.php/Talk:Telescope_Simulator page where we should post questions? [17:16] agree with akhand [17:16] but just going through code wont be effective [17:17] Yes, use this as a general discussion page. If I don't answer you can email me or catch me on IRC. But all discussions/questions should go on that page if possible so we can all benifit [17:18] You all seem to understand English very well [17:19] Yeah we do [17:19] language would not be a constraint in our case i suppose [17:19] yeah [17:19] So, anything we need to discuss? i am going to finidh the first draft of the Architecture document and start the Detailed Design Document. We should all start becomming active at http://setiquest.org/wiki/index.php/Talk:Telescope_Simulator [17:20] "finish", not "finidh" [17:20] finish [17:21] Maybe this will be a short meeting. [17:21] jrseti:just wanted you people would be idling here [17:21] wanted to ask [17:22] I will try to be in the IRC more often, just idling [17:23] Pjaya: could you post the topics of this discussion today at http://setiquest.org/wiki/index.php/Talk:Telescope_Simulator_Status#May_26.2C_2011 [17:23] yeah sure actually it's a short gap in exams so would be goin through the code would need jst little help from your side if possible [17:23] Akhand: OK, great [17:23] yes. I ll do [17:23] Pjaya: great [17:24] Anything else? [17:24] *** khrm got netsplit. [17:24] No lets call it a day [17:24] no for me [17:24] I'll get back to the Architecure document [17:24] bye, thanks. Make sure you are watching http://setiquest.org/wiki/index.php/Talk:Telescope_Simulator [17:24] Sure and i would get to the code [17:25] bye [17:25] me too [17:25] bye [17:25] bye [17:26] Akhand: one more thing. Feel free to edit http://setiquest.org/wiki/index.php/Telescope_Simulator_BackendServer when you learn anything [17:27] Sure i think exact details where to find out the commands and how to enlist them would be helpful to us [17:30] *** khrm got lost in the net-split. [17:30] *** khrm joined #setiquest. [17:41] *** khrm left irc: Ping timeout: 248 seconds [17:56] jrseti:there?? [17:56] *** khrm joined #setiquest. [18:03] Akhand: i am back [18:03] sorry to disturb you [18:04] butn do we have to just look for the commands handled in dispatchcommand [18:04] function [18:04] *** khrm left irc: Ping timeout: 246 seconds [18:04] *** Pjaya left irc: Ping timeout: 252 seconds [18:06] Yes, all commands that are handled in the dispatchCommand() method [18:08] i mean the program has two more Socket there one for Monitor and Other for Alarm [18:08] Dont we have to handle them [18:09] Good question. The Monitor socket sends status back to the Seeker. So we have to document those. You are correct. [18:09] The Alarm also. [18:11] And also the dispatchcommand function categories are quiet different from what being mentioned in the original documents [18:11] few of which are not yet implemented like Stow\ [18:11] "stow" [18:12] Yes, that is part of the problem. Stow is not actually used, so we would not want to document Stow. But we may wish to document which commands are defined but not used. [18:14] and the categories being mentioned in the document like antenna commands,Beamformer commands,Beamformer Misc commands do we have to go by it [18:15] i mean they are bit ambiguous [18:16] we could go by the categories as handled in programs like stop commands Tune commands etc [18:16] *** khrm joined #setiquest. [18:17] Maybe we should document the ones that are actually used and worry about categorizing them later? [18:18] I completed the first draft of http://setiquest.org/wiki/index.php/Telescope_Simulator_Architecture [18:18] We should all comment/improve [18:20] Thats really great!! [18:20] we could only modify it as we get to know more and more about the System [18:20] yes [18:22] I am now creating the Design Document. this will be like the Architecture document but it will be where we describe the details, including the format of the JSON commands. [18:22] jrseti: That would be good but is there any specific reason for using JSON not XML [18:23] I started using JSON in previous projects and found it really useful. Plus, using JSON in Java is really easy with the Jackson software package. [18:25] JSON is used a lot for internet communication and webservices. We could have used XML, but I thought JSON may be easier to use if we ever decide to turn any of this into a webservice. [18:26] JSON is really good but for the webservice front i suppose XML is the one most widely used [18:26] yes. [18:27] Altghough XML is more extensible in terms of structure than JSON [18:28] JSON could be directly ported in JAVAScript thats the feature which made it famous in Ajax applications [18:29] With JSON we could create a webpage that displays the antenna statuses directly from the AntennaSimulator [18:30] Although for our purpose JSON or XML hardly make a difference [18:30] Yes, I think that any messages we need to pass around will be pretty simple. [18:31] one question regarding that Seeker would be using JSON to interact will it be reprogrammed for that [18:32] *** khrm left irc: Ping timeout: 246 seconds [18:33] *** khrm joined #setiquest. [18:33] We should make the BackendServer simulator accept both JSON and the original ASCII commands. We'll try to get it to work with the seeker first in ASCII [18:33] i mean Seeker now uses ASCII commands will it be reprogrammed to use JSON [18:34] Eventually we will have to add this capability to the Seeker [18:34] Or we could design an Middle interface which converts the ASCII commands to JSON [18:34] yes [18:35] *** khrm1 joined #setiquest. [18:35] so that Seeker need not to be reprogrammed [18:35] one question is Seeker controlled by humans [18:35] yes, that is most desirable. [18:36] The seeker can be controlled by humans, or be run in script mode. [18:37] So humans must be issuing Pure String commands in that case Middle interface to convert ASCII to JSON would be great [18:37] so as to keep the original system intact [18:38] *** khrm left irc: Ping timeout: 264 seconds [18:39] Not quite. The Seeker issues these commands as the result of simple commands typed in by the user. Currently there is no way for the user to directly tell the seeker what backendServer command to send. [18:39] Ok [18:39] For development it may be best to develop a program that allows us to select and send these ascii commands to the BackendServer [18:42] Hmm one more thing for going about finding commands we will have to divide work [18:42] yes [18:42] so can we go by dividing the commands based on individual function handling it [18:43] yes [18:43] i mean for the working purpose that would be good to mark all the functions which contain a particular set of commands [18:44] *** Nick change: khrm1 -> khrm [18:44] yes [18:44] and then choose from one of them [18:45] yes, that would be good [18:45] so can i add to the http://setiquest.org/wiki/index.php/Telescope_Simulator_BackendServer page the set of fucntions which handle commands along with line number [18:45] which you could add as a sub issue [18:45] yes, that would be good [18:46] and later a sample procedure to figure commands out of them could be added so that it could be completed easily [18:48] yes [18:49] Ok i will do the above work... [18:56] *** khrm left irc: Quit: Leaving. [18:56] *** khrm joined #setiquest. [19:01] *** khrm left irc: Ping timeout: 246 seconds [19:16] *** khrm joined #setiquest. [19:22] *** khrm left irc: Ping timeout: 252 seconds [19:36] *** khrm joined #setiquest. [19:45] *** khrm left irc: Ping timeout: 246 seconds [20:08] *** Adityab joined #setiquest. [20:37] *** Adityab left irc: Ping timeout: 244 seconds [20:39] *** Adityab joined #setiquest. [20:43] *** akhand left irc: Quit: Page closed [21:00] *** devon_hillard left irc: Read error: Connection reset by peer [22:17] Adityab: How is it going? Please feel free to ask me any Algorithms project questions you might have. [23:44] *** Adityab left irc: Ping timeout: 240 seconds [00:00] --- Fri May 27 2011