>>Have a look at the manual page for 'tagged streams'. That should clear things up.
done! i'm not an expert now but i can work with it and figure out the errors.
>>No way to tell! Try creating a stack trace, or narrowing down which block is triggering this.
done, too! i have tested each block and found out that the "ofdm carrier allocator" block causes the error. i searched for that on the internet and even on the mailing list and found out that it caused by a division by zero. but i can't figure out where this occured and what i have to change to avoid this. any idea which parameter is responsible for that?
some questions for error searching in general: is there a possibility to pinpoint the exact block who causes the error? what do you mean with "creating a stack trace"? are there pages/tutorials/papers to get deeper into this?
thanks!
alphonso