tidal-users Mailing List for TIDAL Tools for Respiratory Physiology
Brought to you by:
sjenkins
You can subscribe to this list here.
2003 |
Jan
|
Feb
(4) |
Mar
(1) |
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(2) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(14) |
From: Steven J. <ste...@ie...> - 2004-07-21 20:20:44
|
The first release candidate for 3.11.4 is on SourceForge. The primary objective of 3.11.4 is adding full support (acquisition and graphics) for Debian sarge. The Installation Guide has instructions to install Comedi and TIDAL on a fresh installation of sarge. Steve |
From: Steven J. <ste...@ie...> - 2004-06-13 07:47:10
|
It turns out that most of the changes I made to suppport GTK+2.0 in Release 3.11.2 are backward compatible with GTK1.2. I've enhanced the configure script to improve detection of libraries and headers; as long as the versions of GTK+ and GConf are compatible with each other (i.e., both pre-GNOME2 or both GNOME2 or later, or GConf absent), TIDAL 3.11.3 should compile successfully on both older and newer Linux platforms. Steve |
From: Harry R. <hro...@uc...> - 2004-06-04 17:24:11
|
Dear Denham Ward and Bill Voter, I am (or rather was) Brian Whipp's PhD student and am currently doing my post-doc at UCSD. Next academic year I will be taking a faculty position in Sue Ward's department in Leeds UK. I have some questions about TIDAL that I think you might be able to help with. We are still running TIDAL on Brian's old 386 computer from UCLA from way-back-when. I would very much like to swap machines to use the LINUX version of TIDAL that, as I understand from Steve Jenkins, you have been using for a couple of years. What I would like to know is the spec's of the computer you have running TIDAL and whether you still use the Data Translation A/D boards? We have some money that will disappear VERY soon and want to buy a Linux machine and new boards, but I have very little experience with Linux and wonder if you could make some recommendations regarding hardware? Further to this we might get a laptop to make a more portable version of the system; again something I have a feeling you have done. Could you let me know the spec's of either the desktop or laptop machines and let me know what to avoid at this early stage. For instance, I had terrible problems when I updated the DOS-based machine to a pentium as there were hard-wired delays in the code (which have now been fixed) which meant a series of small headaches in getting TIDAL to run. I am keen to avoid similar problems. Any help you could provide would be greatly appreciated. Also, (as usual) I am sorry that I am going to have to make these decisions in a hurry (as the money will vanish in a couple of weeks), so any haste you can provide in your response would be very welcome. Many thanks for your advice in advance. and best wishes, Harry Harry B Rossiter, PhD Research Fellow Division of Physiology University of California, San Diego Tel: +1 (858) 822 2321 Fax: +1 (858) 534 4812 |
From: <ben...@id...> - 2004-05-22 12:08:26
|
Dear Open Source developer I am doing a research project on "Fun and Software Development" in which I kindly invite you to participate. You will find the online survey under http://fasd.ethz.ch/qsf/. The questionnaire consists of 53 questions and you will need about 15 minutes to complete it. With the FASD project (Fun and Software Development) we want to define the motivational significance of fun when software developers decide to engage in Open Source projects. What is special about our research project is that a similar survey is planned with software developers in commercial firms. This procedure allows the immediate comparison between the involved individuals and the conditions of production of these two development models. Thus we hope to obtain substantial new insights to the phenomenon of Open Source Development. With many thanks for your participation, Benno Luthiger PS: The results of the survey will be published under http://www.isu.unizh.ch/fuehrung/blprojects/FASD/. We have set up the mailing list fa...@we... for this study. Please see http://fasd.ethz.ch/qsf/mailinglist_en.html for registration to this mailing list. _______________________________________________________________________ Benno Luthiger Swiss Federal Institute of Technology Zurich 8092 Zurich Mail: benno.luthiger(at)id.ethz.ch _______________________________________________________________________ |
From: Steven J. <ste...@ie...> - 2003-05-13 08:14:39
|
Tonight I found and fixed a potentially serious bug that's been in the code since at least 1988. Daq was neglecting the ambient pressure in the conversion to STPD (and using 760 mmHg instead.) I need to make a test case for that, but I went ahead and released 3.10.10 with the fix in it. I did a simple check and it was correct. Steve |
From: Steven J. <ste...@ie...> - 2003-05-04 18:11:41
|
The architecture of TIDAL applications is essentially a general-purpose scripting language engine with data acquisition capability and some built-in constructs that relate to respiratory physiology. When I first conceived of TIDAL in the mid-1980s, the idea of scripting languages was well-established in the Unix world, but the existing languages were not particularly powerful programming environments. It was the right decision at the time to create a new language and embed the necessary application specifics into it. The overwhelming majority of the code in TIDAL is utterly general-purpose; it neither has nor needs any knowledge of respiratory physiological applications. Most of my plans for future enhancements are similarly generic: graphical interfaces, multithreading, etc. In 2003, several powerful scripting languages exist, offering object orientation, multithreading, graphics, extension mechanisms, etc. Among such languages are Perl, Python, Ruby, and Tcl. It is certainly possible in principle to implement all of TIDAL in any of these languages, with the possible exception of the real-time device driver interface. Extensions and tools exist, however, to simplify wrapping the Comedilib interfaces into scripting languages. One example is SWIG. Because these scripting languages are object-oriented, it would be straightforward to implement the fundamental TIDAL data types (channel, phase, and scalar, as well as other internal concepts such as sample and frame). I would estimate that the roughly 10,000 lines of C in TIDAL could be rewritten, with substantially more functionality, in 1000 lines of Python or Ruby. Re-implementing TIDAL in a scripting language would mean the end of EDL. The features of EDL (and much more) would be implemented in objects, and the user's program would simply make direct use of them in the scripting language. The big advantage is that the user would not have to learn a special-purpose language. There are many books and other resources available to anyone wanting to learn Perl, Python, or Ruby. At this point, I'm just mulling some ideas over. The idea of rewriting TIDAL in Python or Ruby is very intriguing. (I don't really care for Perl syntax.) Ruby, for example, has bindings for GTK+ and Tk, which would simplify creation of graphical output and graphical user interfaces. It has native support for threads, which would greatly simplify programming the internal data handling. (A great deal of the complexity in TIDAL is due to the fact that the original MS-DOS platform had very poor support for multithreading in any form.) As of May 2003, I've done some simple prototyping with Ruby and I believe the concept is workable. Steve |
From: Steven J. <ste...@ie...> - 2003-03-25 05:29:47
|
TIDAL 3.10.9 is released. See the Release Notes at http://sourceforge.net/project/shownotes.php?group_id=70327&release_id=148657. There are fixes for two trivial bugs, a new diagnostic script, and some updates to the documentation. I decided to go ahead and release these changes under the "Release Early, Release Often" doctrine. Steve |
From: Steven J. <ste...@ie...> - 2003-02-23 16:34:38
|
TIDAL 3.10.8 is released. From the Release Notes: --------------- Bug 672250 (rsq == 0 on flow channels) is fixed. Bug 670801 (error in viewport y-axis labels) is fixed. A new axis label generating routine was adapted from code in plplot. There is an interim response to RFE 682146 (resize viewport). The initial viewport window size is now controlled by GConf parameters. A new chapter has been added to the User's Guide with illustrative examples. There is some minor cleanup in CVS and release packaging. --------------- The fix for Bug 672250 has been applied to the MS-DOS branch (but not tested) and released as 3.10.3. Things are very busy for me at JPL these days; I plan to concentrate now on updating the documentation as time permits. If a serious bug crops up, I'll try to get to it quickly. Steve |
From: Steven J. <ste...@ie...> - 2003-02-10 04:09:06
|
Bug 670801 (error in viewport y-axis labels) has been reopened. The previous (provisional) fix doesn't really solve the problem. |
From: Steven J. <ste...@ie...> - 2003-02-08 16:40:44
|
I've put an interim response to RFE 682146 (resize viewport) into the upcoming 3.10.8 release. It's in the CVS tidal-3-10-patches branch but not in the head. The viewport driver does not remember what it has previously drawn on the screen, so resizing the window after creating the backing pixmap is currently impossible. I'm looking into a way to allow dynamic resizing when the window is first opened. In the meantime, you can set the viewport window size with gconf parameters /apps/tidal/viewport/maxx and .../maxy. The default window size is 800 x 600. Steve |