[qopen] error on MacOS with multiprocessing / data load

[Tom Eulenfeld]

Hi Manuel,

yes, if you only have the SAC files, you'll need to iterate over them 
and create the XML files from scratch.
Here is the relevant ObsPy code for stationXML
http://docs.obspy.org/tutorial/code_snippets/stationxml_file_from_scratch.html
Similar code for the events is in the Obspy codebase (i.e. 
obspy/io/sh/evt.py).

Hope it helps!
Tom


On 02.05.2018 15:48, Jaimes Caballero, Manuel Alejandro wrote:
> Hi Dr. Eulenfeld,
> 
> That sounds perfect. The line that you provided seems to fix the issue. 
> do you know if event and stations XML files can be created from .SAC 
> files, I know all the information is contained in the header but I do 
> not know if the XML files would have to be created from scratch.
> 
> Thanks for your cooperation,
> 
> Manuel Jaimes.
> 
> On Wed, May 2, 2018 at 9:52 AM, Tom Eulenfeld <tom.eulenfeld at uni-jena.de 
> <mailto:tom.eulenfeld at uni-jena.de>> wrote:
> 
>     Hi Manuel,
> 
>     let's move the conversation to the mailing list as other people
>     might be interested, too.
> 
>     The work-around confirms that the
>     __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNTIONALITY___YOU_MUST_EXEC__()
>     error on MacOS has to do with multiprocessing. Still it's a bit
>     disappointing to use only one core if more are available. After some
>     googling I found out, that it is probably also related to the maxosx
>     backend of matplotlib which does not allow to plot in several
>     subprocesses.
>     Can you please try another backend by starting Qopen with
> 
>     python -c "import matplotlib as mpl; import qopen; mpl.use('agg');
>     qopen.core.run_cmdline()"
> 
> 
>     It should be possible to use SAC files, but additionally you'll need
>     Event and Station XML files. If you need further assistance, let me
>     know.
> 
>     Cheers,
>     Tom
> 
> 
> 
>     On 02.05.2018 13:56, Jaimes Caballero, Manuel Alejandro wrote:
> 
>         Dr. Eulenfeld,
> 
>         Thanks for your quick reply!, the program seems to work like
>         that and it takes less than 5 minutes. I'm wondering if it'd be
>         possible to use .SAC files as the input files, or would I need a
>         .xml file for stations and events?, I could not find anything
>         regarding that on seistools, I found that there was a similar
>         procedure for the program yam but I do not know if it applies
>         the same to qopen?
> 
>         Thanks a lot,
> 
>         Manuel Jaimes.
> 
>         On Wed, May 2, 2018 at 6:02 AM, Tom Eulenfeld
>         <tom.eulenfeld at uni-jena.de <mailto:tom.eulenfeld at uni-jena.de>
>         <mailto:tom.eulenfeld at uni-jena.de
>         <mailto:tom.eulenfeld at uni-jena.de>>> wrote:
> 
>              In the meantime you can try
> 
>              qopen --njobs 1
> 
>              which does not use the multiprocessing module.
> 
>              Cheers,
>              Tom
> 
> 
> 
>              On 02.05.2018 10:25, Tom Eulenfeld wrote:
> 
>                  Hi Manuel,
> 
>                  no, I've never encountered this issue before.
> 
>                  Do you mind opening a new ticket on github?
>         https://github.com/trichter/qopen/issues
>         <https://github.com/trichter/qopen/issues>
>                  <https://github.com/trichter/qopen/issues
>         <https://github.com/trichter/qopen/issues>>
> 
>                  Cheers!
>                  Tom
> 
> 
>                  On 01.05.2018 17:19, Jaimes Caballero, Manuel Alejandro
>         wrote:
> 
>                      Hi Dr. Eulenfeld,
> 
>                      I have been trying to use your software qopen, the
>                      installation process and everything until qopen
>         --tutorial
>                      works perfectly, when I try to run qopen in the
>         terminal it
>                      gives an error which says: Break on
>                     
>         __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNTIONALITY___YOU_MUST_EXEC__()
>                      to debug.
> 
>                      Have you encountered this issue before or do you
>         know what
>                      might be the cause? I'm using macOS.
> 
>                      Thanks for your time.
> 
>                      Manuel Jaimes.
> 
> 
>