ns2 error " o14 cmd line 1 "
Hi all!
I believe some of you are familiar with the following error Code:
(_o14 cmd line 1) Thanks in advance for your time and help! |
That's a generic output ( Or lookalike ) from any error.
I.e. the text with the real error is not shown in post #1. You will have to show this : $ ns wrls-crumor-a30node.tcl , ... followed by the next lines, until the above text. ( And please do not repeat the post #1 error text.) - |
hi knudfi
this is the error as you asked but am afraid it is the full error Code:
foxyrow@foxyrow-HP-Compaq-dc5800-Small-Form-Factor:~/ns-allinone-2.34/ns-2.34/lscrumor$ ns wrls-crumor-a30node.tcl |
# 3 . Well, then you will have to upload the file.
Please attach as 'wrls-crumor-a30node.tcl.txt' Attachment : The paper clip tool in the 'Advanced Editor'. - |
1 Attachment(s)
hi
please find attached the tcl.file |
Hi all
just to close this thread, it has been a while since i post it but i solved the problem. if you encounter this problem it is probably in the file ns2.xx/tcl/lib/ns-lib.tcl that you have to look. it could be a spelling mistake or a wrong instanciation of procedure. i dont recall what was the problem in my case but after correcting the ns-lib.tcl file and saving everything it went well. hope it helps. |
Quote:
thanks a lot in advance |
Quote:
Please upload the modified the ns-lib.tcl file. Thanks in advance. |
SAME problem
_o14 cmd line 1)
invoked from within "_o14 cmd addr" invoked from within "catch "$self cmd $args" ret" How did you rectify this error? Please let us know. |
what change u make sir?
sir can tell s how u solved your problem, cause we have sam problem here
which one code modify in ns-lib.tcl? regrad |
Re post #10, @cahyaindra.
Please explain what you are trying to do .... ? Which errors ? And which protocol are you working with ? |
the same problem r0w225
hi,anyone can explain how solved the problem or upload a file lib-tcl thnx r0w225 can you answer
|
Quote:
|
Re #13.
RUMOR files rumor-ns234-files-2010.tar.gz https://drive.google.com/file/d/0B7S...ew?usp=sharing ns-2.34/tcl/ns-lib.tcl : Is included. |
hello
we have this file but we need only the edited file ns-lib.tcl or if you can explain more how to solve it |
@dadi1004
? Which RUMOR simulation example causes your error ? |
Rumor routing protocol
Quote:
num_nodes is set 31 warning: Please use -channel as shown in tcl/ex/wireless-mitf.tcl (_o14 cmd line 1) invoked from within "_o14 cmd addr" invoked from within "catch "$self cmd $args" ret" invoked from within "if [catch "$self cmd $args" ret] { set cls [$self info class] global errorInfo set savedInfo $errorInfo error "error when calling class $cls: $args" $..." (procedure "_o14" line 2) (SplitObject unknown line 2) invoked from within "_o14 addr" ("eval" body line 1) invoked from within "eval $node addr $args" ("default" arm line 2) invoked from within "switch -exact $routingAgent_ { DSDV { set ragent [$self create-dsdv-agent $node] } DSR { $self at 0.0 "$node start-dsr" } AODV { set ragent [$self cre..." (procedure "_o3" line 14) (Simulator create-wireless-node line 14) invoked from within "_o3 create-wireless-node" ("eval" body line 1) invoked from within "eval $self create-wireless-node $args" (procedure "_o3" line 23) (Simulator node line 23) invoked from within "$ns node" ("for" body line 2) invoked from within "for {set i 0} {$i < $val(nn) } { incr i } { set node_($i) [$ns node] }" (file "wrls-crumor-a30node.tcl" line 66) |
Re #17, @dadi1004.
The file "wrls-crumor-a30node.tcl" : The LSCRUMOR protocol is unknown to me. Please upload the LSCRUMOR files to 'Google Drive' or to a pastebin site. And show links to the "LSCRUMOR files" in a new post. |
Quote:
Sir, can you let me know how you solved this problem. I am too getting the same error. Kindly please HELP! |
Post #19, @palreg.
The shown errors are generic. Can happen from "any" faulty file.tcl . Or by using a wrong copy of the executable 'ns'. Required information : Please show your command. And most important : Attach a copy of your "simulation.tcl". |
All times are GMT -5. The time now is 08:55 PM. |