{"action":"created","issue":{"url":"https://api.github.com/repos/megies/obspyck/issues/85","repository_url":"https://api.github.com/repos/megies/obspyck","labels_url":"https://api.github.com/repos/megies/obspyck/issues/85/labels{/name}","comments_url":"https://api.github.com/repos/megies/obspyck/issues/85/comments","events_url":"https://api.github.com/repos/megies/obspyck/issues/85/events","html_url":"https://github.com/megies/obspyck/issues/85","id":382575452,"node_id":"MDU6SXNzdWUzODI1NzU0NTI=","number":85,"title":"NLLoc running","user":{"login":"rcabdia","id":22215772,"node_id":"MDQ6VXNlcjIyMjE1Nzcy","avatar_url":"https://avatars2.githubusercontent.com/u/22215772?v=4","gravatar_id":"","url":"https://api.github.com/users/rcabdia","html_url":"https://github.com/rcabdia","followers_url":"https://api.github.com/users/rcabdia/followers","following_url":"https://api.github.com/users/rcabdia/following{/other_user}","gists_url":"https://api.github.com/users/rcabdia/gists{/gist_id}","starred_url":"https://api.github.com/users/rcabdia/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rcabdia/subscriptions","organizations_url":"https://api.github.com/users/rcabdia/orgs","repos_url":"https://api.github.com/users/rcabdia/repos","events_url":"https://api.github.com/users/rcabdia/events{/privacy}","received_events_url":"https://api.github.com/users/rcabdia/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2018-11-20T09:37:33Z","updated_at":"2018-11-26T13:35:06Z","closed_at":null,"author_association":"NONE","body":"From I've read till now is that previously to run FocMec to calculate \r\nthe Focal Mechanism, I need to locate the epicenter with NLLoc. \r\n\r\nBecause I've read that might be there will be problems with Mac I've moved to a Linux machine.\r\nIn this email, I write a complete description of the architecture folders that I followed to run Nlloc but unfortunately something wrong happened. I've tried to be the most clear with my issue as possible for not making you waste any time.\r\n\r\nRight now I have this installation scheme\r\n\r\n/home/sysop/miniconda2/envs/obspyck_test/lib/python2.7/site-packages/obspyck\r\n\r\nin this folder I've created the subfolder plugins in which I've created \r\n\r\n/home/sysop/miniconda2/envs/obspyck_test/lib/python2.7/site-packages/obspyck/focmec\r\n/home/sysop/miniconda2/envs/obspyck_test/lib/python2.7/site-packages/obspyck/hyp_2000\r\n/home/sysop/miniconda2/envs/obspyck_test/lib/python2.7/site-packages/obspyck/nlloc\r\n\r\nInside the ./nlloc there are the typical executable files NLLoc, Grid2Time and so on....\r\n\r\nNow, to run my example, I've created in my desktop a folder named obspyck with this architecture\r\nhome/Escritorio/obspyck/nlloc\r\n\r\ninside the obspyck/nlloc folder there are the waveforms, the file.cfg and I've also created a symbolic link NLLoc ---> NLLoc__Linux__64bit\r\n\r\nfollowing the issue #11\r\n\r\nFor the output\r\nhome/Escritorio/obspyck/nlloc/loc1\r\n\r\nFor the travel times \r\nhome/Escritorio/obspyck/nlloc/time\r\n**[layer.P.sta.buf,layer.P.sta.hdr,layer.S.sta.buf,layer.S.sta.buf]\r\n\r\nAnd the run/control file named locate_BY.nlloc in the previous folder \r\n\r\nhome/Escritorio/obspyck/locate_BY.nlloc\r\nwhich is attached in this email and the LOCFILES line is\r\n\r\nLOCFILES ./nlloc.obs NLLOC_OBS ./time/layer ./loc1\r\n**From the #issue11 I guess that nlloc.obs is created after pick the waveforms and saved in the folder from Ive run obspyck//in my case home/Escritorio/obspyck/nlloc.\r\n**I ve also guessed that obspyck always look for the nlloc control file inside locate_BY.nlloc.\r\n\r\nAfter this configuration, I0ve run successfully obspyck and I picked some waveforms but when I run do_nlloc, obspyck cannot find nlloc. I attached the log error file. \r\n\r\nI forget mention you that moreover NLLoc is also in the path of my computer, \r\nI thought that everything is right but I missed in some point and I am stack,\r\n\r\nPlease  could anyone\r\n[log2.txt](https://github.com/megies/obspyck/files/2599023/log2.txt)\r\n\r\n[example_cfg.txt](https://github.com/megies/obspyck/files/2599028/example_cfg.txt)\r\n[locate_BY.nlloc.txt](https://github.com/megies/obspyck/files/2599029/locate_BY.nlloc.txt)\r\n\r\n\r\n guide me to find a way-out.\r\n"},"comment":{"url":"https://api.github.com/repos/megies/obspyck/issues/comments/441640633","html_url":"https://github.com/megies/obspyck/issues/85#issuecomment-441640633","issue_url":"https://api.github.com/repos/megies/obspyck/issues/85","id":441640633,"node_id":"MDEyOklzc3VlQ29tbWVudDQ0MTY0MDYzMw==","user":{"login":"megies","id":1842780,"node_id":"MDQ6VXNlcjE4NDI3ODA=","avatar_url":"https://avatars1.githubusercontent.com/u/1842780?v=4","gravatar_id":"","url":"https://api.github.com/users/megies","html_url":"https://github.com/megies","followers_url":"https://api.github.com/users/megies/followers","following_url":"https://api.github.com/users/megies/following{/other_user}","gists_url":"https://api.github.com/users/megies/gists{/gist_id}","starred_url":"https://api.github.com/users/megies/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/megies/subscriptions","organizations_url":"https://api.github.com/users/megies/orgs","repos_url":"https://api.github.com/users/megies/repos","events_url":"https://api.github.com/users/megies/events{/privacy}","received_events_url":"https://api.github.com/users/megies/received_events","type":"User","site_admin":false},"created_at":"2018-11-26T13:35:06Z","updated_at":"2018-11-26T13:35:06Z","author_association":"OWNER","body":"> Something I've noticed is that when obspyck write the observation file \"nlloc.obs\", it does not >include the polarities U, D (is attached also)\r\n\r\nCan't say for sure, but I think I never used polarities with NLLoc. Does Nlloc even use polarities?\r\n\r\n> When I write the location file.xml, the coordinates of the location are different from the location of >the file .hyp. (very strange) I can imagine that the problem comes from the config file (it is attached). it >also is shown when I plot the map, the wrong location. it could be because of the transformation >\"TRANS SIMPLE\" of the control file? may be because it can be read properly the lat long and depth >from the file.hyp.\r\n\r\nThere is some coordinate conversion mechanics in util.py, see \r\n - https://github.com/megies/obspyck/blob/74df05a9be4c08ef318d8a08fc0599045e6a1eb2/obspyck/util.py#L981-L1003\r\n - https://github.com/megies/obspyck/blob/master/obspyck/obspyck.py#L2395\r\n\r\nThis is also mentioned in one of the other NLLoc issues here, you might have to patch this in your obspyck installation, sorry, never got round to make this changeable via config file, I think.\r\n\r\n\r\n---\r\n\r\nNot sure what the problem with focmec is, but you should try to run the focmec binary from command line, it should ask for all the input info then, just to see if your binary works.."}}
{"actor":{"display_login":"megies"}}