Fixed limits on operation is all solved in HSP2?

[scalet98]

As long as I know, fortran version HSPF has a limited no. of operation. Therefore, there was a limitation on the application of LULC or Reach. According to your program specification, there were no more fixed limits on operations.

" Restructure for maintainability, to remove fixed limits (e.g., operations, land use,
   parameters), and to maintain or improve execution time."

Then we don't need to construct the model separately due to the functional limitation when applying HSP2. Right?

Best regards. Jiheon Lee.

[JasonLoveRespec]

There is not a functional (fixed number of operations) limitation. There is still a practical reason to divide the model up into a logical number of operations.

JASON LOVE, P.E. Senior Vice President

605.394.6512 office // 605.484.2380 cell

---

From: Jiheon Scarlett Lee notifications@github.com Sent: Thursday, March 28, 2019 5:16 AM To: respec/HSPsquared Cc: Subscribed Subject: [respec/HSPsquared] Fixed limits on operation is all solved in HSP2? (#24)

As long as I know, HSPF has a limited no. of operation. Therefore, there was a limitation on the application of LULC or Reach. According to your program specification, there were no more fixed limits on operations.

" Restructure for maintainability, to remove fixed limits (e.g., operations, land use, parameters), and to maintain or improve execution time."

Then we don't need to divide the model due to the functional limitation when applying HSP2. Right?

Best regards. Jiheon Lee.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/respec/HSPsquared/issues/24, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AcYK3gYlXDEvLGL1H-D7hu2LMEgoS8anks5vbKSogaJpZM4cP6La.

Confidentiality Notice: This E-mail and any attachments is covered by the Electronic Communications Privacy Act, 18 U.S.C. & 2510-2524, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, and permanently delete the original and destroy any copy, including printed copies of this email and any attachments thereto.

[scalet98]

Hello!~ JASON !

Thank you for your kind and quick reply. I understand what you mean. Last time, while constructing the model, I have faced difficulties due to the limitations of operation. At first time, I did not know that limited no. of operation is possible in HSPF model.

Anyhow, now your HSP2 does not have any limitations. I welcome HSP2. I don't need to separate the model intentionally, as long as I use HSP2. For sure, I will divide the model if it is required logically.

Thank you again.

Jiheon Lee

---

Ji-Heon Lee Ph. D. Candidate Dep. of Urban Engineering Chungbuk National University

Tel : +82-43-275-3478 Fax : +82-43-275-3478 Cellphone : +82-10-2745-2316 E-mail : career03@hotmail.comhttp://mail2.daum.net/hanmail/mail/MailComposeFrame.daum?TO=career03%40hotmail.com

---

보낸 사람: Jason Love notifications@github.com 보낸 날짜: 2019년 3월 28일 목요일 오후 8:51 받는 사람: respec/HSPsquared 참조: Jiheon Scarlett Lee; Author 제목: Re: [respec/HSPsquared] Fixed limits on operation is all solved in HSP2? (#24)

There is not a functional (fixed number of operations) limitation. There is still a practical reason to divide the model up into a logical number of operations.

JASON LOVE, P.E. Senior Vice President

605.394.6512 office // 605.484.2380 cell

---

From: Jiheon Scarlett Lee notifications@github.com Sent: Thursday, March 28, 2019 5:16 AM To: respec/HSPsquared Cc: Subscribed Subject: [respec/HSPsquared] Fixed limits on operation is all solved in HSP2? (#24)

As long as I know, HSPF has a limited no. of operation. Therefore, there was a limitation on the application of LULC or Reach. According to your program specification, there were no more fixed limits on operations.

" Restructure for maintainability, to remove fixed limits (e.g., operations, land use, parameters), and to maintain or improve execution time."

Then we don't need to divide the model due to the functional limitation when applying HSP2. Right?

Best regards. Jiheon Lee.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/respec/HSPsquared/issues/24, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AcYK3gYlXDEvLGL1H-D7hu2LMEgoS8anks5vbKSogaJpZM4cP6La.

Confidentiality Notice: This E-mail and any attachments is covered by the Electronic Communications Privacy Act, 18 U.S.C. & 2510-2524, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, and permanently delete the original and destroy any copy, including printed copies of this email and any attachments thereto.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/respec/HSPsquared/issues/24#issuecomment-477563411, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AurA-nswYsMr_WnkrSRAw4PVQC0SXkutks5vbKzbgaJpZM4cP6La.