Siege Performance Test Result Parameters

I'm using siege to test a website, and I entered the following command {code ...} the following result is displayed: {code ...} why is this transactions 1300 instead of 100? Does reponsetime mean the average response time? Concurrency is the most... I'm using siege to test a website, and I entered the following command

siege -c 10 -r 10 -f test.txt

The following result is displayed:

Transactions:                1300 hitsAvailability:              100.00 %Elapsed time:                3.99 secsData transferred:            0.54 MBResponse time:                0.01 secsTransaction rate:          325.81 trans/secThroughput:                0.13 MB/secConcurrency:                2.82Successful transactions:         100Failed transactions:               0Longest transaction:            1.04Shortest transaction:            0.00

Why is this transactions 1300 instead of 100? Does reponse time mean the average response time? What is the highest concurrency of concurrency?
How can I use siege to log on first and then test it?

Reply content:

I'm using siege to test a website, and I entered the following command

siege -c 10 -r 10 -f test.txt

The following result is displayed:

Transactions:                1300 hitsAvailability:              100.00 %Elapsed time:                3.99 secsData transferred:            0.54 MBResponse time:                0.01 secsTransaction rate:          325.81 trans/secThroughput:                0.13 MB/secConcurrency:                2.82Successful transactions:         100Failed transactions:               0Longest transaction:            1.04Shortest transaction:            0.00

Why is this transactions 1300 instead of 100? Does reponse time mean the average response time? What is the highest concurrency of concurrency?
How can I use siege to log on first and then test it?