Charting and OPK conflicting info

Liv279

Member
Joined
Nov 5, 2012
Messages
10
Reaction score
0
I just started charting this cycle for the first time after using OPKs for the past 2 years. Unfortunately I didn't start charting until day 6 of my cycle but I figured I would continue anyway. My temps have been increasing each day and today (day 9) it went from 97.23 to 97.59. Writing it here doesn't look like much of a change but on the chart it does! However, my OPK shows no signs yet of a positive.

How much of a temp spike normally indicates OV?
Is a daily increase in temp an indication that OV is coming soon?
Is there a chance that the OPK could be wrong and the temp chart right?

Does anyone else OV early?
My gut feeling is that I have been OV early and that's why we're missing it because the OPK has always given a positive later in my cycle when I start testing from day 10. That's why I decided to start the OPK tests earlier this time.

Thanks for any input
 
Keep taking your temperature, 1 high temp doesn't mean much, you want sustained higher than before temperatures.

Where are you charting? You can use fertilityfriend.com and it will show you when you ovulated; even better, you can post a link to your graph so we all can give it a look:)

I personally hate opks because i have had mixed results. But, have you tried testing twice a day from around cd 10? Maybe you are just missing the surge

I hope this helps, good luck
 
As what morasmum said, keep taking your temp, 1 high temp doesn't mean anything.

If you look at my chart, i do have 1 high temp before O, and I O early, day 11 or 12. OPK is positive only for 1 day on the day of ovulation. Before I gave birth to my first child i use to O day 14 or 15, and OPK is positive for 3 days before I can see my temp spike showing ovulation.
 
I personally find opk's infinitely more reliable than temps, and numerous studies have found that the lh surge is much more precise at framing ovulation than temperature charts. I don't bother with temps at all.
 
Due to my PCOS, it is not uncommon at all for me to have ups and downs like you did pre-ovulation. You can look at my chart (click in my sig) and see for yourself. Also, I am on my second cycle of using the OvaCue Fertility Monitor because after 4 cycles of using OPKs and temping, we weren't getting anywhere. The first month using OvaCue, it hinted that I actually get my LH surge the evening of the day I ovulate... so more than likely, after I have ovulated. I talked to one of the OvaCue specialists and she said she sees that a lot. Some women just don't produce enough LH to get a positive on an OPK, or if they do, it is processed too late. The OvaCue bases off electrolytes that track your estrogen and progesterone levels. I use both the oral and vaginal sensors with it, and it has given me a lot of insight. You just have to be careful about your sodium intake as well as any medications you are taking. This past cycle I did not have much success with the OvaCue because my doctor put me on Apidex-P (phentermine) for weight loss and it REALLY screwed up my cycles and hormones. I have quit taking it because of all of the side effects, so I expect my OvaCue to be back on track next month.

So... it IS possible that you ovulate before an OPK tells you and temping will not predict ovulation for you. It can only give you a general idea that it happened. Best thing is to get to know your cycle through temping, then you will have a better idea of your 'window' unless you have irregular cycles like I used to. (I have PCOS) After even one cycle of temping, you have a better guesstimate of where your fertile window is. If you ovulated on CD 14 (your temp went up at least .2 and stayed up for at least 3 days) then next cycle, start the BD'ing around CD10 and keep it going until 2 days after ovulation. Then your bases are covered. :)

Good luck!
 

Users who are viewing this thread

Members online

No members online now.

Latest posts

Forum statistics

Threads
1,650,284
Messages
27,143,880
Members
255,747
Latest member
Leoniee
Back
Top
monitoring_string = "c48fb0faa520c8dfff8c4deab485d3d2"
<-- Admiral -->