archive-edu.com » EDU » W » WASHINGTON.EDU

Total: 718

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Support #363: Update NCEDC web service entry in server-side web services config file. - JWEED - IRIS SeisCode
    that the NCEDC web service specified in the server list is http www ncedc org ws bulkdataselect This web service will soon be deprecated and has been replaced by our FDSN equivalent http service ncedc org fdsnws dataselect 1 Could you please make the appropriate change in your list of servers Based on the JWEED manual it looks like the server list is updated dynamically from IRIS DMC Thanks Stephane

    Original URL path: https://seiscode.iris.washington.edu/issues/363 (2015-06-03)
    Open archived version from archive


  • Support #348: check web service configurations to ignore old IRIS ws - JWEED - IRIS SeisCode
    still attempting to connect to www iris edu ws which is being deprecated This may be due to old settings that remain fixed in place after installation and in the current implementation is probably not removed even if our http accessible server list file is modified The following steps are suggested to correct this issue Make sure that a new build of JWEED does not have www iris edu ws hardcoded into the install config Ensure that the IRIS FDSN web services reference is the default Make sure that the http accessible server list has the www iris edu ws entry removed Some current users may find that they are still attempting to connect to the old services and this will become a growing problem as we begin to shut those servers down We will have to guide users to change their server defaults in their config when this happens In the next release of JWEED it may be desirable to have a smarter system of deleting bad server entries from a remote file or to simply have the JWEED update make a backup of the old server config and replace it with the new and improved config The reason

    Original URL path: https://seiscode.iris.washington.edu/issues/348 (2015-06-03)
    Open archived version from archive

  • Version 1 - History - Wiki - Wiki - mseed2sac - IRIS SeisCode
    below f format The default output format is binary SAC with the same byte order as the host computer This option forces the format for every output file 1 Alphanumeric SAC format 2 Binary SAC format host byte order default 3 Binary SAC format little endian 4 Binary SAC format big endian N netcode Specify the network code to use overriding any network code in the input Mini SEED S station Specify the station code to use overriding any station code in the input Mini SEED L location Specify the location code to use overriding any location code in the input Mini SEED C channel Specify the channel code to use overriding any channel code in the input Mini SEED r bytes Specify the Mini SEED record length in bytes by default this is autodetected i Process each input file individually By default all input files are read and all data is buffered in memory before SAC files are written This allows time series spanning mutilple input files to be merged and written in a single SAC file The intention is to use this option when processing large amounts of data in order to keep memory usage within reasonable limits Metadata Files A metadata file contains a list of station parameters some of which can be stored in SAC but not in Mini SEED Each line in a metadata file should be a list of parameters in the order shown below Each parameter should be separated with a comma or a vertical bar Dip Convention When comma separators are used the dip field CMPINC is assumed to be in the SAC convention degrees from vertical if vertical bars are used the dip field is assumed to be in the SEED convention degrees from horizontal and converted to SAC convention Metadata fields Network KNETWK Station KSTNM Location KHOLE Channel KCMPNM Latitude STLA Longitude STLO Elevation STEL in meters not currently used by SAC Depth STDP in meters not currently used by SAC Component Azimuth CMPAZ degrees clockwise from north Component Incident Angle CMPINC degrees from vertical Instrument Name KINST up to 8 characters Scale Factor SCALE Scale Frequency unused Scale Units unused Sampling rate unused Start time used for matching End time used for matching Example with comma separators with SAC convention dip net sta loc chan lat lon elev depth azimuth SACdip instrument scale scalefreq scaleunits samplerate start end IU ANMO 00 BH1 34 945981 106 457133 1671 145 328 90 Geotech KS 54000 3456610000 0 02 M S 20 2008 06 30T20 00 00 2599 12 31T23 59 59 IU ANMO 00 BH2 34 945981 106 457133 1671 145 58 90 Geotech KS 54000 3344370000 0 02 M S 20 2008 06 30T20 00 00 2599 12 31T23 59 59 IU ANMO 00 BHZ 34 945981 106 457133 1671 145 0 0 Geotech KS 54000 3275080000 0 02 M S 20 2008 06 30T20 00 00 2599 12 31T23 59 59 IU ANMO 10 BH1 34 945913 106 457122

    Original URL path: https://seiscode.iris.washington.edu/projects/mseed2sac/wiki/Wiki/1 (2015-06-03)
    Open archived version from archive

  • Bug #350: v1.0.0 produces very large file that doesn't seem to include all channels - FDSN StationXML-SEED Converter - IRIS SeisCode
    09 12 2013 Priority Normal Due date Assignee Yazan Suleiman Done 0 Category Target version Resolution Description These files can be examined at wilber3 data adam 2013 04 20 mw66 sichuan china on dmc3 4 or wilber bash 4 1 ls l total 358472 rw r r 1 www daemon 59947008 Sep 12 15 39 2013 04 20 mw66 sichuan china miniseed rw r r 1 www daemon 208152 Sep 12 16 06 channel list rw r r 1 www daemon 12058624 Sep 12 16 06 seed dataless rw r r 1 www daemon 294125568 Sep 12 15 39 test dataless seed dataless was produced by v0 0 98 and when combined with this miniseed file in rdseed produces a 91MB output file that appears to have all 1300 channels test dataless was produced by v1 0 0 It is much larger but when run through rdseed produces a 7MB output file with only 100 or so channels I tried loading the second file with obspy xseed and it failed with the message SEEDParserException More than one Volume index control header found History 1 Updated by Adam Clark over 1 year ago Assignee set to Chad Trabant I got another

    Original URL path: https://seiscode.iris.washington.edu/issues/350 (2015-06-03)
    Open archived version from archive

  • Activity - Celso Reyes - IRIS SeisCode
    s activity From 01 26 2015 to 02 24 2015 02 24 2015 01 42 PM irisFetch Feature 579 Resolved Add support for writing structured data to SAC OK I think this should do it to write out either trace

    Original URL path: https://seiscode.iris.washington.edu/activity?from=2015-02-24&user_id=6 (2015-06-03)
    Open archived version from archive

  • Feature #579: Add support for writing structured data to SAC - irisFetch - IRIS SeisCode
    months ago Done changed from 0 to 80 Estimated time set to 20 00 spent 13h20m implementing and writing into irisFetch Right now I just have a couple small items dates to touch on before I consider it a good rough draft ready to release for testing further tweaking and comments Questions 1 Should we do anything with SAC Poles and Zeros I m assuming at this point that kind of thing doesn t actually go into a sac file so I m ignoring it 2 How should the user access the ability to save SAC files I propose a routine parallel to irisFetch Traces called irisFetch Sacfiles This would have a similar signature but with an additional required parameter writeDirectory which could be blank If blank it indicates the current MATLAB path The same functionality is accessible via the Traces method by adding a WRITESAC option For example irisFetch Traces IU ANMO 00 BH 2010 02 27 06 30 00 2010 02 27 10 30 WRITESAC c Users someone sacfiles which is equivalent to irisFetch Sacfiles IU ANMO 00 BH 2010 02 27 06 30 00 2010 02 27 10 30 c Users someone sacfiles However irisFetch sacfiles accepts NO output arguments Data goes only to disk while doing these modifications I ve added a couple new Trace options that could help with debugging ASJAVA the java objects are returned instead of MATLAB structs 3 The ISYNTH flag should it be set Since it was really quick to do I added a test for network SY with appropriate checks for locations S1 S3 and their respective channels If these match up then the ISYNTH flag can be turned on 4 Data Quality Should that be set IRIS data quality flags aren t the same as the SAC quality flags IQUAL Should they be set If so how should they be mapped 5 Scale factor SCALE Should this be set form somewhere 3 Updated by Chad Trabant 6 months ago Questions 1 Should we do anything with SAC Poles and Zeros I m assuming at this point that kind of thing doesn t actually go into a sac file so I m ignoring it Let s not do anything with it for now We could write them out to annotated SAC PZ files like the irisws sacpz service produces but let s think about it a bit 2 How should the user access the ability to save SAC files I propose a routine parallel to irisFetch Traces called irisFetch Sacfiles This would have a similar signature but with an additional required parameter writeDirectory which could be blank If blank it indicates the current MATLAB path This sounds good to me I think we ALSO need a way to write an existing Trace structure out to SAC This would allow for example a user to access data via irisFetch Traces performs some pre processing and then save to the disk in SAC 3 The ISYNTH flag should it be set Since

    Original URL path: https://seiscode.iris.washington.edu/issues/579 (2015-06-03)
    Open archived version from archive

  • Version 12 - History - Wiki - Wiki - irisFetch - IRIS SeisCode
    Help Online Manual Instructions and usage examples exist in the online manual section available from http www iris edu dms nodes dmc software downloads irisFetch m 2 0 2 manual Web Seminar Examples of using irisFetch was included in a web seminar webinar from November 8 2012 This webinar starts with general information about web services 1 00 then discusses retrieving event and trace data via the browser 8 45

    Original URL path: https://seiscode.iris.washington.edu/projects/irisfetch/wiki/Wiki/12 (2015-06-03)
    Open archived version from archive

  • Bug #407: 8bits ascii char in dataless - FDSN StationXML-SEED Converter - IRIS SeisCode
    Main java 197 at edu iris converter Main main Main java 216 ESCA dataless 368 KB Catherine Pequegnat 12 11 2013 04 47 PM History 1 Updated by Chad Trabant over 1 year ago Assignee set to Yazan Suleiman 2 Updated by Yazan Suleiman over 1 year ago Status changed from New to Feedback I have a work around version 1 0 3 should deal with that At this point this is an issue in the network description field The file in question will be very helpful 3 Updated by Catherine Pequegnat over 1 year ago File ESCA dataless added here is the file see B050F10 4 Updated by Catherine Pequegnat over 1 year ago with stationxml converter 1 0 3 jar java jar home sysop resifMdi stationxml converter 1 0 3 jar x l resp se RESIF so RESIF o ESCA sta xml ESCA dataless ERROR with Integer field value for fieldNum 10 and fieldIndex 0 forcing value of zero blktype 0 value e 0 5 Updated by Celso Reyes over 1 year ago Yes it looks like it is not looking into the extended character set at all for neither program Notice that the values wrap So at a minimum the error message display is incorrect It looks like it s probably wrapping within the range of 128 to 127 For example the radical symbol checkmark is 512 17 26 while the R is extended ASCII value 174 128 46 I wonder if this same sort of error is propagated elsewhere in the system It should be looking at probably unsigned integers instead of signed char or equivalent When I try it with PDCC 3 8 I get WARNING character value 26 is not acceptable for Blockette 50 field 9 Expected one of UpperCase LowerCase Digit Punctuation Space

    Original URL path: https://seiscode.iris.washington.edu/issues/407 (2015-06-03)
    Open archived version from archive



  •