Q from a novice user in Japan

Dear GNUradio experts,

I am very new to GNUradio. I am in Kyoto University, Japan studying
ionosphere by using radar and other techniques. I am interested
in developing a 150/400MHz beacon receiver with GNUradio + USRP.
Now I have a USRP base board + Basic RX + Flex 400 for this purpose.

I have some questions.

— Are there any Japanese users of GNUradio + USRP?

— How I can get information on Python functions?
Documents generated by “doxygen” explain only
C++ part of the software. (Am I correct?)
To know Python functions, do I need to read through
codes? I would like to know if there is a list
or man-pages of such Python functions. My application
may not require any new C++ coding.

— I learned GNUradio and USRP from network very much.
Thank you very much. But informations are very much
scattered. Don’t you have a plan of GNUradio (plus USRP) book?

Thanks for your help. Regards,


Mamoru Y. [email protected]

On Thu, Nov 09, 2006 at 03:30:28AM +0900, Mamoru Y. wrote:

Dear GNUradio experts,

I am very new to GNUradio. I am in Kyoto University, Japan studying
ionosphere by using radar and other techniques. I am interested
in developing a 150/400MHz beacon receiver with GNUradio + USRP.
Now I have a USRP base board + Basic RX + Flex 400 for this purpose.

OK.

A TV RX daughterboard might be a better choice for the 150 MHz beacon.

I have some questions.

— How I can get information on Python functions?
Documents generated by “doxygen” explain only
C++ part of the software. (Am I correct?)
To know Python functions, do I need to read through
codes? I would like to know if there is a list
or man-pages of such Python functions. My application
may not require any new C++ coding.

You could run epydoc on the python code in and under
gnuradio-core/src/python.
Most of the code has epydoc doc strings.

— I learned GNUradio and USRP from network very much.
Thank you very much. But informations are very much
scattered. Don’t you have a plan of GNUradio (plus USRP) book?

We’ve thought about it. Thanks for the words of encouragement.

Thanks for your help. Regards,

Mamoru Y. [email protected]

You’re welcome.

Eric

On Thursday 09 November 2006 05:31, Eric B. wrote:

— How I can get information on Python functions?
Documents generated by “doxygen” explain only
C++ part of the software. (Am I correct?)
To know Python functions, do I need to read through
codes? I would like to know if there is a list
or man-pages of such Python functions. My application
may not require any new C++ coding.

You could run epydoc on the python code in and under
gnuradio-core/src/python. Most of the code has epydoc doc strings.

Tried that. Running epydocs’ last stable (2.1) release didn’t produce
anything
useful. It complaint about improper paragraph indentation for most of
the
files. Haven’t tried their developement version - yet.

cheerio Berndt

Dear Colleagues,

Yesterday I re-installed the “epydoc” from the subversion
repository of epydoc, and tried formatting the GNUradio
python libraries. epydoc version would be 3.0, I suppose.

The result was much better than before. Though I met
some errors, I could generate useful HTMLs with which I can
browse python functions. Thanks for Eric’s suggestion.

I also learned that after “import” any module in python,
we can show its help information by typing “help(module)”.
Sorry I am too ignorant to this software package.

Regards,


Mamoru Y. [email protected]

I installed ver 2.1 from yum (Fedore Core 4), and run it.

Dear GNUradio experts,
I have some questions.

— How I can get information on Python functions?
Documents generated by “doxygen” explain only
C++ part of the software. (Am I correct?)
To know Python functions, do I need to read through
codes? I would like to know if there is a list
or man-pages of such Python functions. My application
may not require any new C++ coding.

You could run epydoc on the python code in and under gnuradio-
core/src/python.

G’day,

I’ve also built epydoc 3.0alpha3 and tried to generate documentation run
it
against ${PYSITELIB}/gnuradio. It produced a lot of documentation but it
failed prior to finishing. There were a lot of warnings and the process
failed in wxgui.

If someone was successful in completing the conversion, perhaps it may
be a
good idea to make the documentation available as a package. I certainly
would
appreciate it.

Thanks,

cheerio Berndt

Eric,

Thank you for your answer.

For our applicaion 150MHz and 400MHz receivers must synchronize
very precisely. I cannot use TV RX for this reason. Is the
frequency 150MHz too high for Basic RX board? We may need
to add more amplifiers between the antenna and the USRP.

Thank you very much for the information of “epydoc”.
I installed ver 2.1 from yum (Fedore Core 4), and run it.
But as other E-mail says, I got many errors. It created
some results, but I do not know if they are very useful
or not… Should I use Ver 3.0 of the epidoc?

Regards,

Mamoru Y.

A TV RX daughterboard might be a better choice for the 150 MHz beacon.

Mamoru Y. [email protected]

You’re welcome.

Eric


Mamoru Y. [email protected]

Mr. Berndt,

I tried the same. Running epydoc against /usr/local/lib…/gnuradio
failed. That looked very close to the end, and must have generated
a good package of manual HTMLs of everything. I hope someone can
fix the problem.

After this fail, I tried to run it for each package of
gnuradio-core, and gr-usrp. This was successful. Specifying
the directory name was sometimes successful. If not,
I specified like “…/*.py”. I do not know this is the
correct way or not. I experienced several errors in the
process. But generated HTMLs look useful enough.

Regards,

Mamoru Y.

G’day,

I’ve also built epydoc 3.0alpha3 and tried to generate documentation run
it
against ${PYSITELIB}/gnuradio. It produced a lot of documentation but it
failed prior to finishing. There were a lot of warnings and the process
failed in wxgui.

If someone was successful in completing the conversion, perhaps it may
be a
good idea to make the documentation available as a package. I certainly
would

Yesterday I re-installed the “epydoc” from the subversion

very precisely. I cannot use TV RX for this reason. Is the

Mamoru Y.

On Thu, Nov 09, 2006 at 03:30:28AM +0900, Mamoru Y. wrote:

Dear GNUradio experts,

I am very new to GNUradio. I am in Kyoto University, Japan
studying

ionosphere by using radar and other techniques. I am interested
in developing a 150/400MHz beacon receiver with GNUradio + USRP.
Now I have a USRP base board + Basic RX + Flex 400 for this
purpose.

OK.

A TV RX daughterboard might be a better choice for the 150 MHz
beacon.

You could run epydoc on the python code in and under gnuradio-

core/src/python.

Most of the code has epydoc doc strings.

— I learned GNUradio and USRP from network very much.
Thank you very much. But informations are very much
scattered. Don’t you have a plan of GNUradio (plus USRP)
book?