Error in AMY creation from NOAA data

weather-data
#1

I am trying the new Dragonfly (great tool, thank you). I am trying to develop the AMY for Jakarta. I have the following error:

I have attached the relevant files (gh file, the NOOA file, and the EPW) that I used.

  1. Any idea why this happened?
  2. Will this component work for multiple year NOOA data?

nooa.zip (717.1 KB)

0 Likes

#2

cc: @chris, @SaeranVasanthakumar

0 Likes

#3

@erydjunaedy ,

I should mention that we are still working on making the AMY file generation more stable and bugs are to be expected in this component right now, especially given that some NOAA data sources can have very bad data quality. My best recommendation for the time being might just be to wait until we have the more stable method for generating AMY files finished, which should be in a couple of months. If you really need the AMY file, cleaning the data manually in excel might be the best route.

And I can confirm that the component is only meant to use a single year’s-worth of AMY data.

0 Likes

#4

Did anyone find the solution to the amy creation. @chris i am getting the same error.

0 Likes

#5

@Asisnath ,

Admittedly, that component that I built was really not coded well. Not only did I not use the best methods to account for estimating missing data like solar radiation but I did not code it to handle the wide array of situations that you encounter in the NOAA database (including a lot of holes in some data sets).

What I can say is that I just finished a pull request to the Ladybug[+] Core Library that adds nearly everything that is needed to build this workflow correctly. So I can put together some components that use these methods soon after we merge in that pull request (which should be within a week or so).

In the meantime, the best that I can offer is either manually processing the NOAA data or, if you know python, you can clone my branch of the Ladybug[+] core repository and use the EPW object, zhang-huang sky model, and a few other functions to help you process some of the data.

1 Like

#6

thanks @chris , will be waiting for an update to this.

0 Likes

#7

Hello All,

I apologize for the late response here but I have finally gotten around to updating the Grasshopper script that creates AMY files from the NCDC data:
http://hydrashare.github.io/hydra/viewer?owner=chriswmackey&fork=hydra_2&id=Create_Actual_Meteorologic_Year_EPW

The new Grasshopper definition works with the new format of the NCDC data and it should be much more reliable across different sources of data in the NCDC.

ALSO, PLEASE NOTE THAT YOU NEED THE MOST UP-TO-DATE VERSION ON THE LADYBUG[+] LIBRARIES IN ORDER FOR THE GRASSHOPPER FILE TO RUN CORRECTLY.

2 Likes

#8

@chris thanks a lot chris and i tried it. One Question chris i tried to update dragonfly with dragonfly update component and still it doesn’t updates the components to April version. Can you please guide how to get the latest version.
Thanks Asis

0 Likes

#9

I also noticed this and checked that those DF components belong to DF +, which are not public yet (at least didn’t find them).
So in the meantime this example is the source.
-A.

0 Likes

#11

@Asisnath and @AbrahamYezioro ,

You are right @AbrahamYezioro, that these components are a part of a new revision of Dragonfly that is in the works right now (aka. DragonflyPlus).

DragonflyPlus is currently hardcore WIP and the only components that are not placeholders are the ones in that updated Hydra example. I haven’t even put in a component to update the other components yet so that is why I wasn’t telling people to install them in their toolbars. Still, if you are willing to manually reinstall them later once they inevitably get updated, you can find the userobjects in this repository: https://github.com/ladybug-tools/dragonfly-grasshopper

All of our work is always public but we might sometimes put it in an obscure repo if we are not yet ready to deal with a ton of support requests about it :slight_smile: !

0 Likes

#12

Hello @chris. I tried with my location 2010 data and i came through this error.

6956787895513dat.txt (420.7 KB)
6956787895513stn.txt (449 Bytes)

It is working fine with paris data you provided. Is it a bug?

0 Likes

#13

This is the “dark” LB … :sunglasses:

0 Likes

#14

@Asisnath ,
Thanks for reporting the issue. It happened because your file did not contain any data about air pressure at the location of the weather station. However, the file has plenty of data on the pressure at sea level so I made a change in the code to substitute station pressure data with sea level pressure data whenever it is missing:

I also updated the hydra example such that you can now use it to create an EPW for your txt file. As a head’s up, it looks like the time zone of your location is a bit odd:

0 Likes

#15

@chris, It worked perfectly now. Yes i too find the timezone a bit odd, nevertheless i will test this component with few other places. Thanks for the update.

0 Likes