Skip to main content

Adding a cap to a logarithmic regression

I'm running a log regression to model out reach curves. A typical reach curve looks like: reach curve

So using a log regression seems the obvious choice. The reach curves are based on historical activity, but I have some additional knowledge of the total user count, so I know for certain that the reach can never exceed a certain number.

I am having a hard time blending a modelled log curve with a known hard cap. Ideally I think I should add some modifier that increases the diminishing effect as the output approaches the known cap, to help preserve the curve on the lower values (where most the activity happens) while adding in the known cap to prevent the model from returning values where the reach is 125% of all users.

Currently i'm using scipy optimize, i've added a ton of synthetic data at the known max to try and force this model to respect the max, but I think i'm going down the wrong road here:

current model

I feel like I need another function that takes the output of this one, and adds a penalty increasing in strength as the value approaches the known max, but I can't seem to get it to work, my curve keeps going negative or the blend comes out really jarring like a hard cap, any thoughts on how to approach this?



source https://stackoverflow.com/questions/77448229/adding-a-cap-to-a-logarithmic-regression

Comments

Popular posts from this blog

Confusion between commands.Bot and discord.Client | Which one should I use?

Whenever you look at YouTube tutorials or code from this website there is a real variation. Some developers use client = discord.Client(intents=intents) while the others use bot = commands.Bot(command_prefix="something", intents=intents) . Now I know slightly about the difference but I get errors from different places from my code when I use either of them and its confusing. Especially since there has a few changes over the years in discord.py it is hard to find the real difference. I tried sticking to discord.Client then I found that there are more features in commands.Bot . Then I found errors when using commands.Bot . An example of this is: When I try to use commands.Bot client = commands.Bot(command_prefix=">",intents=intents) async def load(): for filename in os.listdir("./Cogs"): if filename.endswith(".py"): client.load_extension(f"Cogs.{filename[:-3]}") The above doesnt giveany response from my Cogs ...

How to show number of registered users in Laravel based on usertype?

i'm trying to display data from the database in the admin dashboard i used this: <?php use Illuminate\Support\Facades\DB; $users = DB::table('users')->count(); echo $users; ?> and i have successfully get the correct data from the database but what if i want to display a specific data for example in this user table there is "usertype" that specify if the user is normal user or admin i want to user the same code above but to display a specific usertype i tried this: <?php use Illuminate\Support\Facades\DB; $users = DB::table('users')->count()->WHERE usertype =admin; echo $users; ?> but it didn't work, what am i doing wrong? source https://stackoverflow.com/questions/68199726/how-to-show-number-of-registered-users-in-laravel-based-on-usertype

Where and how is this Laravel kernel constructor called? [closed]

Where and how is this Laravel kernel constructor called? public fucntion __construct(Application $app, $Router $roouter) { } I have read the documentation and some online tutorial but I can find any clear explanation. I am learning Laravel and I am wondering where does this kernel constructor receives its arguments from. "POSTMOTERM" CLARIFICATION: Here is more clarity.I have checked the boostrap/app.php and it is only used for boostrapping the interfaces into the container class. What is not clear to me is where and how the Kernel class is instatiated and the arguments passed to the object calling the constructor.Something similar to; obj = new kernel(arg1,arg2) or, is the framework using some magic functions somewhere? Special gratitude to those who burn their eyeballs and brain cells on this trivia before it goes into a full blown menopause alias "MARKED AS DUPLICATE". To some of the itchy-finger keyboard warriors, a.k.a The mods,because I believe in th...