Go into the folder where the .jar ( NS workbench application is ) for eg: C:NSNAM> ns sim.tcl. The sim.tcl is the script file. Both the script file name and the trace file name can me named as per your choice under Configuration pull down menu. Trace file and the script file will be created in the directory where the application file (.jar) is resides.

You can specify the file name for trace file, tcl script file, and nam file by going to configuration ? trace. All units in web server properties, web client, as well as TCP transport and sink and CBR transport are in byte and second.

A.Yes, you can change the name of your trace file. You need to go to "Configuration" and click on "Trace" and make the necessary changes. No, you may not be able to open a .nsb file (created on an older version of NSBench) in the newer version of NSBench. No, its not neccessary to have a web cache between the web server and the client unless required, the webserver and the client can be connected directly.

Bytes. We have to convert the bytes to bits and then to Mbits. i.e. multiply the size by 8 and then divide by 10^6.

The Gerald module of the SolexaPipeline generates a FASTQ-like format, but it is not a FASTQ in fact. You should convert the format with "maq sol2sanger". This page gives more explanation. The latest SolexaPipeline-0.3.0 generates a new file in the "Export" format. Read sequences, qualities and most of alignment information is stored in this file.

The xrpcc tool does in fact generate the WSDL file, but due to a bug it gets deleted along with the source files if the -keep option is not specified. You can use the -keep option which will cause xrpcc to not delete the WSDL or .java source files. If you also use the -s sourcepath option, all of the source files will be placed in the sourcepath directory and then you can easily delete them. The WSDL file will still be placed in the current directory or the directory specified by the -d option.

When you generate trace file in the Dos Command line, you can see node name and its corresponding number which is used in the trace file. e.g.

You must use GET_TARGET_PROPERTY to obtain the location of the generated executable. Some platforms put executables in separate directories according to their build type, i.e. MSVC typically has subdirectories for "Debug" and "Release" builds. For the DEPENDS part of the command, you can either use DOIT_EXE or just simply use the name of the target. This will ensure that the target doit is built before any target that uses the output from the custom command.

ADIF support is not currently built into CT. Instead, download C2A.ZIP and unpack it into your CT directory. The file is run by typing (at a DOS prompt): This will generate a file named <log>.ADI which can be imported into your logging program. There are other command-line options, see the README.TXT file included in the archive. You can read more about ADIF by following this link.

The Make16.bat file automatically generates a listing file for your program. In the following command, taken from the file, the -Fl is the listing file parameter:

All you need is to have the Adobe PDF Writer package installed on your computer. Then from the HTML viewer, simply click the print icon. Then ensure the printer output is the Adobe Distiller or Adobe PDFWriter. It is that simple!

The ADD_CUSTOM_COMMAND command lets you generate a source file that you can then include in another target. For example: ADD_CUSTOM_COMMAND( OUTPUT ${CMAKE_CURRENT_BINARY_DIR}/foo.c COMMAND ${CMAKE_COMMAND} copy ${CMAKE_CURRENT_SOURCE_DIR}/bar.c ${CMAKE_CURRENT_BINARY_DIR}/foo.c DEPENDS ${CMAKE_CURRENT_SOURCE_DIR}/bar.c ) ADD_EXECUTABLE(foo foo.c) This will create an executable by copying bar.c to foo.c and then compiling foo.c to produce foo.

This will cause a verilog.dump file to be created in the current directory. For long simulations the verilog.dump file can get very large.

Click on the "XML" link before the "General Information" section on the detail page, or the "XML" link for each entry on the multiple results page.

It is possible to replay frame files captured using Codima tools (i.e., autoVoIP? and autoAnalyzer? Consultancy Kits), as well as trace files from Ethereal? This is done using the Flow Analyzer, which breaks down the call into dialogs, covering Signaling, Media and Reporting for both the incoming and outgoing flow.

Unfortunately, *.Jet is our internal binary format and we are not planning to public its description in the near future because of our desire to reserve the right for its change. For export into MapInfo it is enough to use the "Export" command. You should attentively think over export options, as if you have not selected layers for export you wouldn't receive any file. MapInfo data structure requires each layer to be exported into separate file.

Make sure that the Poisson Request Sequence in the Web client setting is lower than the simulation time.

If it is not specified, the default unit is either "byte" for size or "second" for time.

What does the following mean? 40% of the users use FTP, 40% of the users use WWW and 20% use UDP audio. I don't see the application when I double click the nsBench-1.0b3.jar file; instead I see all class files. This happens when you associate nsBench-1.0b3.jar with WinZip or WinRar. You will need to open it using javaw.exe. For windows, right click the file and select "open with" and click on "Select Program" and then "Browse" and give the path of javaw.exe. For a default installation of Java1.