Hi,
> On 18 Feb 2016, at 12:15, Gerrit Holl wrote:
>
> Hi,
>
> I have so far been a bad boy and not done any proper test driven
> development or indeed any unit tests. What are the plans for typhon?
> Writing unit tests is time consuming but I've repeatedly had
> situations where a unit test c
Hi,
> On 18 Feb 2016, at 12:10, Gerrit Holl wrote:
>
> Hi,
>
> On 18 February 2016 at 06:50, Oliver Lemke
> wrote:
>>> currently, typhon has a dependency on Python 3.3, numpy (no version
>>> specified), and scipy (the same).
>>
>> To be hones
Hi all,
We're happy to announce that typhon can now be directly installed in anaconda
environments without a detour through pip. To install typhon just run:
conda install -c rttools typhon
If you're not using anaconda for your python workflow yet, we highly recommend
to give it a try:
http://
Hi Gerrit,
> On 26 Feb 2016, at 17:06, Gerrit Holl wrote:
>
> [snip]
>
> Would it be wise to add the svnversion to any unreleased version of
> typhon, such that the version would be 0.2.7+9733, until we reach
> 0.2.8?
Although I'm usually an opponent of svn keywords ;-), it makes perfect sense
Hi Gerrit,
> On 17 Mar 2016, at 19:46, Gerrit Holl wrote:
>
> Hi,
>
> On 29 February 2016 at 07:10, artswebserv...@gmail.com
> wrote:
>> Log:
>> * typhon/__init__.py:
>>
>> Add revision to version number for development releases.
>
> $Revision$ in __init__.py won't work, regrettably. This i
Hi Gerrit,
Let's keep it optional for now.
cheers,
/oliver
> On 23 Mar 2016, at 20:13, Gerrit Holl wrote:
>
> Hi,
>
> I'd like to add some progressbars to routines,
>
> https://pypi.python.org/pypi/progressbar2
>
> can we add this as a dependency or shall I write my code such that
> this i
Hi Gerrit,
> On 16 Sep 2016, at 13:31, Gerrit Holl wrote:
>
> Hi,
>
> On 12 August 2016 at 14:55, artswebserv...@gmail.com
> wrote:
>> Added:
>> typhon/trunk/typhon/thermodynamics.py
>
>> * typhon/thermodynamics.py:
>>
>> Currently containing functions related to water vapor and its thermo
Hi Gerrit,
> On 7 Oct 2016, at 16:04, Gerrit Holl wrote:
>
> On 7 October 2016 at 14:58, Lukas Kluft wrote:
>
>> But I definitely support your point on unit testing.
>
> And which means that to do it properly, we need not only unit testing,
> but unit testing using (at least) the oldest offic
Hi Gerrit,
> On 9 Dec 2016, at 16:40, Gerrit Holl wrote:
>
> On 7 December 2016 at 13:38, artswebserv...@gmail.com
> wrote:
>> Author: lkluft
>> Log:
>> * typhon/spectroscopy.py:
>>
>> Module for spectroscopy related functions. Currently containing a function
>> to calculte the width (full-wid
Hi Gerrit,
> On 6 Jan 2017, at 12:24, Gerrit Holl wrote:
>
> Hi,
>
> I added a ticket on trac related to typhon but there is currently no
> typhon component. I'm not sure if I can add this myself or if this
> requires higher privileges than I have. Oliver, do you know if I can
> add a compone
Hi Gerrit,
Since xarray is available as an anaconda package and developed by the
well-known pydata community, I think it is okay to depend on it. As long as we
don't require a newer version than the one available in the anaconda repository.
cheers,
/oliver
> On 26 Jan 2017, at 17:32, Gerrit H
Hi Gerrit,
> On 6 Feb 2017, at 15:43, Gerrit Holl wrote:
>
> On 6 February 2017 at 14:40, Gerrit Holl wrote:
>> On 6 February 2017 at 13:56, Lukas Kluft wrote:
>>> I had a look at your SRF class but was not able to use it. I get
>>> DimensionalityError when trying to create an object.
>>>
>>>
Hi Olivier,
The SRF class is unit-aware. This means that all values you pass in, must have
the correct unit attached. E.g.:
import typhon
typhon.physics.units.SRF([1e9] * typhon.physics.units.ureg.Hz, [1])
Unfortunately, there is currently a problem with our SRF class which makes it
incompatib
> On 27 Feb 2017, at 16:30, Gerrit Holl wrote:
>
> Hi,
>
>
>
> On 27 February 2017 at 06:38, Oliver Lemke
> wrote:
>> Hi Gerrit,
>>
>>> On 6 Feb 2017, at 15:43, Gerrit Holl wrote:
>>>
>>> On 6 February 2017 at 14:40, Ge
Hi all,
I've restructured the documentation to provide a cleaner overview of what's
available. Compare for example the ARTS module documentation:
Before: http://www.radiativetransfer.org/misc/typhon/doc/typhon.arts.html
After: http://www.radiativetransfer.org/misc/typhon/doc-trunk/typhon.arts.h
Hi Gerrit,
While having the possibility to use UTF-8 characters in variable names in
Python is certainly a neat feature, I have concerns about the usability and
maintainability of such code. I hope you agree that using UTF-8 characters in
function names or keywords (which you don't do here) wou
Hi Gerrit,
It would be fine to add it like that. But can you explain the difference
between your class and the default IntFlag behaviour?
Enumeration values seem to be identical between:
class MyClass1(AutoFlag):
flag0=enum.auto() # 1
flag1=enum.auto() # 2
flag2=enum.auto()
Hi Gerrit,
Why is it necessary to replace .T with .swapaxes? Could you give an example
were the former fails but the latter works?
cheers,
/oliver
> On 22 Aug 2017, at 13:37, Gerrit Holl wrote:
>
> Hi,
>
> I need to adapt typhon.oem.retrieval_gain_matrix to allow
> broadcasting. That would
Hi all,
Today we released typhon version 0.4.0. As usual, it is available through pip
and the anaconda rttools repository.
http://www.radiativetransfer.org/misc/typhon/doc/
You might receive the following error when you import typhon without having a
DISPLAY variable set on Unix:
In [1]: impo
Dear friends and developers of typhon,
To extend the reach and exposure of the typhon project, as well as profiting
from the features of the git version control system, we have come to the
conclusion that it is in the best interest of the project to move the typhon
repository to github.com .
T
/CONTRIBUTING.md
Cheers,
Oliver
> On 13 Sep 2017, at 14:41, Oliver Lemke wrote:
>
> Dear friends and developers of typhon,
>
> To extend the reach and exposure of the typhon project, as well as profiting
> from the features of the git version control system, we have come to the
&g
Hi all,
To remove some overhead to get small changes into typhon, all members of the
typhon developers team[1] have now been granted push rights for the main
repository.
Pull request are still _strongly_ recommended for non-trivial changes. Code
reviews are an essential tool for quality assura
Hi [TP]y[tp]hon friends,
Yesterday, we released Typhon 0.5.0. This version fixes incompatibility with
the latest SciPy 1.0 version for users of the PyPi and Anaconda packages.
This was the last version to maintain compatibility with Python 3.5. The
requirements in the current GitHub version hav
Hi Gerrit,
> On 2 Jan 2018, at 20:01, Gerrit Holl wrote:
>
> Hi,
>
> other github projects I'm on have a wiki link in the top bar, but
> typhon has no such link. Does anyone know why?
>
> When I navigate to https://github.com/atmtools/typhon/wiki I'm simply
> redirected back to https://github
Hi Frederico,
The error you got was a bug in Typhon. It is now fixed in the latest
development version[1].
Note: If you use the ARTS interface in Typhon, it is better to call the ARTS
ReadXML routine to load the lookup table directly into ARTS instead of using
the Typhon reading routine and th
Hi Simon,
> On 5 Feb 2018, at 16:10, Simon Pfreundschuh
> wrote:
>
> Dear all,
>
> Are there any guidelines on how to cite typhon? I couldn't find
> anything in the documentation.
>
> I thought that maybe its also a good idea just to have a bibtex entry
> in the README.md on github.
There is
Hi Reno,
The error messages you get there don't make sense to me. It finds the api in
'/Users/reno/OneDrive/Models/arts-2.2.64/build/build/Debug/src/libarts_api.so',
so the ARTS_BUILD_PATH settings seem to be okay. No clue why directly
afterwards it fails. I have the suspicion that something go
Hi Reno,
Are you using cmake to generate an Xcode project and compile ARTS inside Xcode?
In that case yes, Xcode does put compiled files directly inside the
Debug/Release directory with no additional src subdirectory. According to your
previous log file, you had a libarts_api.so in build/build/
Very soon, it is about time indeed. Just wanted to wait till the collocation
framework is in good shape.
Next week is pretty busy here, so let's aim for week 26?
John, do you think we/you are ready for this? :-)
Anything else we have to clean up before the release?
Cheers,
/oliver
> On 13
> On 13 Jun 2018, at 11:59, Gerrit Holl wrote:
>
> On 13 June 2018 at 10:42, Oliver Lemke wrote:
>>
>> Very soon, it is about time indeed. Just wanted to wait till the collocation
>> framework is in good shape.
>>
>> Next week is pretty busy here, so
Hi all,
We are planning to release Typhon 0.6.0 tomorrow (29.6.). If you are aware of
any showstoppers that need to be fixed before the release, please let me now
today.
cheers,
/oliver
___
typhon.mi mailing list
typhon.mi@lists.uni-hamburg.de
https:
Hi all,
Since Anaconda just added full support for the latest Python 3.7 release, I'm
happy to announce that compatible packages for typhon are now available on the
rttools channel as well.
If like living on the bleeding edge, you can now easily set up a Python 3.7
environment with typhon by r
Hi Gerrit,
> On 14 Jan 2019, at 22:10, Gerrit Holl wrote:
>
> Hi,
>
> is there any way to control what methods are being shown with the
> autosummary method documentation generation? With regular autoclass
> we can control whether inherited methods should be documented or not,
> but our autosu
Hi Gerrit,
Yes, since quite some time has already passed since the last release, it would
fit to make another one. Let's aim for a 0.7 release towards the end of next
week.
Cheers,
Oliver
> On 15 Jan 2019, at 17:04, Gerrit Holl wrote:
>
> Hi,
>
> shall we have a typhon release soon?
>
> I
Hi Manik,
For just reading the data, it is probably easiest to use CODA[1] directly. If
you're using the Anaconda environment, you can install it easily with:
conda install -c stcorp coda
You then read the IASI File like this:
import coda
f =
coda.open('./W_XX-EUMETSAT-Darmstadt,HYPERSPECT+SO
Hi all,
Time flies, it has been a year since the last release. So we're calling this
the "anniversary" release and celebrating by having another one.
• Over 250 commits of bug fixes, documentation improvements and other goodies
since the previous release
• New topography module, using the 1 km
Hi Eric,
Your assumption about the transition to PyARTS is correct. The typhon.arts
module will be eventually removed.
Concerning your OEM retrievals, it is the best approach to facilitate PyARTS
for that already now. All current development effort for the ARTS interface is
going into PyARTS a
, bg=True)
> wmap = worldmap(secondary["lat"], secondary["lon"], s=24, ax=wmap.axes,)
> # colloc only
> wmap = worldmap(
> collocations['primary/lat'],
> collocations['primary/lon'],
> facecolor="r", s=128, marker=
no Picard wrote:
>
> thnx: about the second point, I made my mind and there's probably no need:
> the initial dataset can easily be edited using ".sel" applied to the list of
> selected coordinates...
>
> best,
>
> Bruno
>
> Le 22/06/2021 à 08:07,
Hi PingyiDong,
> On 5 Aug 2021, at 19:20, 董平夷 <20191205...@nuist.edu.cn> wrote:
>
> Dear developers,
>
> I am a postgraduate student in Nanjing University of Information Science and
> Technology in China, my name is Pingyi Dong, I am working on remote sensing
> ice clouds with sub-millimeter w
gt;
>> - the output figures
>>
>>
>>
>> Can you help me on this ?
>>
>> By the way, I can't find a way to increase the level of verbosity for the
>> collocate method: did I miss something ?
>>
>>
>>
>> best,
&g
41 matches
Mail list logo
